qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hellermann <stefan@the2masters.de>
To: Gleb Natapov <gleb@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: How to use -acpitable to add a SLIC-table?
Date: Tue, 31 Mar 2009 18:40:36 +0200	[thread overview]
Message-ID: <49D24784.8030505@the2masters.de> (raw)
In-Reply-To: <20090330163718.GJ25718@redhat.com>

Gleb Natapov schrieb:
> On Mon, Mar 30, 2009 at 05:36:06PM +0200, Stefan Hellermann wrote:
>   
>> Gleb Natapov schrieb:
>>     
>>> On Thu, Mar 26, 2009 at 06:35:16PM +0100, Stefan Hellermann wrote:
>>>   
>>>       
>>>> Hello,
>>>>
>>>> how can I use the -acpitable parameter to add a SLIC-table to the
>>>> qemu-bios dynamically?
>>>>
>>>> I think I need a file with the SLIC-data, but how can I extract this
>>>> data out of my BIOS from my host-machine for example?
>>>>
>>>> The -acpitable parameter accepts a bunch of settings and a datafile, do
>>>> I need to set all these settings? I think most of them should sit in the
>>>> SLIC-file.
>>>>
>>>>     
>>>>         
>>> -acpitable parameter settings are field from common ACPI table header.
>>> If you skip any of them default will be used. Table data that goes after
>>> headers should be specified after data=.
>>>
>>>   
>>>       
>>>> I tried using SLIC-Data-files downloaded from the web, but I'm unsure if
>>>> they are formatted correctly.
>>>>     
>>>>         
>>> It looks like they already contain ACPI header.
>>>   
>>>       
>> Okay, I did some new tries. On my own (real-)machine I did
>> # acpidump -o acpidata
>> # acpixtract -l dump | grep SLIC
>> Signature Length  OemId     OemTableId   OemRevision CompilerId
>> CompilerRevision
>>     SLIC     374  "LENOVO"  "TP-7O   "    00002210    " LTP"     00000000
>> # acpixtract -sSLIC acpidata
>> # qemu-system-x86_64 -acpitable
>> sig=SLIC,rev=1,oem_id=LENOVO,oem_table_id=TP-70\ \ \
>> ,oem_rev=00002210,asl_compiler_id=\
>> LTP,asl_compiler_rev=00000000,data=SLIC.dat
>>
>>     
>
> Are you sure your BIOS is up to date?
>   
 I thought the latest kvm-userspace snapshot should contain a reasonable
good snapshot of qemu, but I was wrong. Somehow kvm managed it to break
the support for -acpitable.

I checked out the latest qemu trunk and now -acpitable works great. Thanks!

But qemu is slow, with -enable-kvm it's also slow .... I think I will
try out kqemu.

Thanks for you patience! I should have checked if plain qemu works ...

Stefan

> --
> 			Gleb.
>
>   

  reply	other threads:[~2009-03-31 16:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-26 17:35 [Qemu-devel] How to use -acpitable to add a SLIC-table? Stefan Hellermann
2009-03-27  7:36 ` [Qemu-devel] " Gleb Natapov
2009-03-30 15:36   ` Stefan Hellermann
2009-03-30 16:37     ` Gleb Natapov
2009-03-31 16:40       ` Stefan Hellermann [this message]
2009-03-31 16:53         ` Gleb Natapov
2009-03-31 21:12           ` Stefan Hellermann
2009-03-30 20:27     ` Andreas Färber
2009-10-28 10:12     ` Michael Tokarev
2009-10-28 11:36       ` Stefan Hellermann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49D24784.8030505@the2masters.de \
    --to=stefan@the2masters.de \
    --cc=gleb@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).