qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Cc: bochs-developers@lists.sourceforge.net,
	Sebastian Herbszt <herbszt@gmx.de>
Subject: Re: [Qemu-devel] Re: [Bochs-developers] [PATCH] Read additional ACPI tables from a VM
Date: Mon, 09 Feb 2009 15:28:52 -0600	[thread overview]
Message-ID: <4990A014.1040202@codemonkey.ws> (raw)
In-Reply-To: <20090209210027.GA13234@redhat.com>

Gleb Natapov wrote:
>>> +
>>> +static int acpi_load_table(int i, uint32_t addr, uint16_t *len)
>>> +{
>>> +    qemu_cfg_read((uint8_t*)len, sizeof(*len));
>>> +
>>> +    if (!*len)
>>> +        return -1;
>>> +
>>> +    qemu_cfg_read((uint8_t*)addr, *len);
>>> +    return 0;
>>> +}
>>> #endif
>>>
>>> void init_smp_msrs(void)
>>>       
>> Can you please diff against bochs cvs?
>>
>>     
> Will do. This patch was initially intended to go to qemu patch series so I
> did it against patched bios source.

I'm happy to update to a more recent BIOS snapshot...

>  And unpatched bochs bios does not
> boot linux with qemu. IRQ routing problem or something.
>   

Unless upstream Bochs has regressed.  Did you apply the other patches in 
the QEMU series?  Some are no longer needed I think.

Regards,

Anthony Liguori

> --
> 			Gleb.
>
>
>   

  reply	other threads:[~2009-02-09 21:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-09 14:30 [Qemu-devel] [PATCH] Read additional ACPI tables from a VM Gleb Natapov
2009-02-09 20:41 ` [Qemu-devel] Re: [Bochs-developers] " Sebastian Herbszt
2009-02-09 21:00   ` Gleb Natapov
2009-02-09 21:28     ` Anthony Liguori [this message]
2009-02-10  7:20       ` Gleb Natapov
2009-02-10 20:28         ` Marcelo Tosatti
2009-02-15 22:22         ` [Qemu-devel] Re: [Bochs-developers] [PATCH] Read additionalACPI " Sebastian Herbszt
2009-02-16 10:14           ` Gleb Natapov

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=4990A014.1040202@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=bochs-developers@lists.sourceforge.net \
    --cc=herbszt@gmx.de \
    --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).