qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Beth Kon <eak@us.ibm.com>
To: Jes Sorensen <jes@sgi.com>
Cc: Kevin O'Connor <kevin@koconnor.net>, qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: [PATCH] Seabios irq override support.
Date: Mon, 27 Jul 2009 14:47:05 -0400	[thread overview]
Message-ID: <4A6DF629.1030802@us.ibm.com> (raw)
In-Reply-To: <4A6D562C.3010103@sgi.com>

Jes Sorensen wrote:
> On 07/25/2009 03:56 AM, Kevin O'Connor wrote:
>> On Fri, Jul 24, 2009 at 03:07:12PM +0200, Jes Sorensen wrote:
>>> With this patch applied, I can boot KVM using the latest upstream QEMU
>>> and Seabios.
>>
>> Thanks Jes.
>>
>> The bochs commit shows this wrapped in "#ifdef BX_QEMU".  Will this
>> patch break bochs, or were the ifdefs just bochs paranoia?
>
> Hi Kevin,
>
> I don't actually know for sure. I didn't add the #ifdefs since I got the
> impression that Seabios doesn't have them in many places. The original
> code was designed by Beth Kon, so maybe she can comment on whether we
> should add them to Seabios.
>
> Beth?
>
> Thanks,
> Jes
Hi Jes. These bios changes rely on matching userspace/kernel changes 
that translate irq0->inti2. So assuming seabios is used for systems 
other than kvm and qemu, this code would need to be conditionally removed.

But I'm not clear on what you're doing with this patch. You didn't 
include the irq0override flag that is needed by kvm because there are 
circumstances under which kvm turns off irq0override (i.e., old kernels 
that don't support irq routing). So this patch is fine for qemu, since 
it is permanently enabled there, but it is not a permanent solution for kvm.

  reply	other threads:[~2009-07-27 18:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-24 13:07 [Qemu-devel] [PATCH] Seabios irq override support Jes Sorensen
2009-07-25  1:56 ` [Qemu-devel] " Kevin O'Connor
2009-07-27  7:24   ` Jes Sorensen
2009-07-27 18:47     ` Beth Kon [this message]
2009-07-28  8:59       ` Jes Sorensen

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=4A6DF629.1030802@us.ibm.com \
    --to=eak@us.ibm.com \
    --cc=jes@sgi.com \
    --cc=kevin@koconnor.net \
    --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).