qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: Kevin O'Connor <kevin@koconnor.net>,
	seabios@seabios.org, qemu-devel@nongnu.org,
	Gleb Natapov <gleb@redhat.com>
Subject: [Qemu-devel] Re: [SeaBIOS] seabios: acpi: add _RMV control method for PCI devices
Date: Mon, 20 Dec 2010 11:15:40 +0200	[thread overview]
Message-ID: <4D0F1EBC.9050205@redhat.com> (raw)
In-Reply-To: <20101220084948.GA16707@amt.cnet>

On 12/20/2010 10:49 AM, Marcelo Tosatti wrote:
> On Sun, Dec 12, 2010 at 02:57:45PM -0500, Kevin O'Connor wrote:
> >  On Sun, Dec 12, 2010 at 09:49:16PM +0200, Gleb Natapov wrote:
> >  >  On Sun, Dec 12, 2010 at 02:11:29PM -0500, Kevin O'Connor wrote:
> >  >  >  On Wed, Dec 08, 2010 at 03:08:59PM -0200, Marcelo Tosatti wrote:
> >  >  >  >  Use _RMV method to indicate whether device can be removed.
> >  >  >  >
> >  >  >  >  Data is retrieved from QEMU via I/O port 0xae0c.
> >  >  >  >
> >  >  >  >  Signed-off-by: Marcelo Tosatti<mtosatti@redhat.com>
> >  >  >
> >  >  >  Thanks Marcelo,
> >  >  >
> >  >  >  Can you add acked-bys from the qemu/kvm maintaners?
> >  >  >
> >  >  Marcelo is kvm maintainer ;) FWIW I tested this with Windows 7&  XP
> >  >  and it works as expected. The patch relies on patch not yes excepted
> >  >  to qemu though.
> >
> >  Yeah - I know - but I figured I'd ask for concensus before committing.
> >  :-)
> >
> >  The committing of seabios patches that have a dependency on qemu/kvm
> >  is an area that I think could be better clarified.  I'm thinking that
> >  if the seabios part depends on something in qemu/kvm then we should
> >  have the corresponding kvm/qemu maintaners "ack" it.
> >
> >  -Kevin
>
> Avi, are you OK with this patch ?
>
> Yes, perhaps it all (including PCI hotplug controller) should be using
> something else than hardcoded IO ports, but thats what we have now.

At least it should be documented.

What's the behaviour with a qemu that doesn't support the new port?  We 
don't strictly support it, but let's do so if we can.

-- 
error compiling committee.c: too many arguments to function

  reply	other threads:[~2010-12-20  9:15 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-08 17:08 [Qemu-devel] seabios: acpi: add _RMV control method for PCI devices Marcelo Tosatti
2010-12-08 17:34 ` [Qemu-devel] " Gleb Natapov
2010-12-08 18:01   ` Marcelo Tosatti
2010-12-08 19:58     ` Gleb Natapov
2010-12-08 21:23       ` Marcelo Tosatti
2010-12-11  7:39 ` [Qemu-devel] Re: [SeaBIOS] " Avi Kivity
2010-12-13  0:00   ` Marcelo Tosatti
2010-12-13  8:41     ` Avi Kivity
2010-12-13  8:49       ` Gleb Natapov
2010-12-13  8:53         ` Avi Kivity
2010-12-13  9:03           ` Gleb Natapov
2010-12-13  9:10             ` Avi Kivity
2010-12-13  9:16               ` Gleb Natapov
2010-12-12 19:11 ` Kevin O'Connor
2010-12-12 19:49   ` Gleb Natapov
2010-12-12 19:57     ` Kevin O'Connor
2010-12-20  8:49       ` Marcelo Tosatti
2010-12-20  9:15         ` Avi Kivity [this message]
2010-12-20 17:05           ` Marcelo Tosatti
2010-12-20 17:44             ` Avi Kivity
2010-12-20 18:23               ` Marcelo Tosatti
2011-01-05 11:10 ` [Qemu-devel] " Gleb Natapov
2011-01-06  2:27   ` [Qemu-devel] Re: [SeaBIOS] " Kevin O'Connor

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=4D0F1EBC.9050205@redhat.com \
    --to=avi@redhat.com \
    --cc=gleb@redhat.com \
    --cc=kevin@koconnor.net \
    --cc=mtosatti@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=seabios@seabios.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).