qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
	seabios@seabios.org, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [SeaBIOS] seabios: acpi: add _RMV control method for PCI devices
Date: Mon, 13 Dec 2010 11:10:38 +0200	[thread overview]
Message-ID: <4D05E30E.20309@redhat.com> (raw)
In-Reply-To: <20101213090359.GA15610@redhat.com>

On 12/13/2010 11:03 AM, Gleb Natapov wrote:
> >  We could also deprecate the old port and use fwcfg for everything
> >  (try fwcfg, fall back to ae00).
> >
> fwcfg designed to be simple for easy use by firmware. It has two port
> one for index another for value, so its use is racy in multi-threaded SMP
> environment. DSDT code is executed in such environment. There is lock
> facility in AML, but why complicate things.

I prefer to remove complexity from interfaces and have it in the 
implementation instead.

> >  >>   We could do this in two ways: by adding a fwcfg client to the DSDT,
> >  >>   or by copying the information to system memory, and referencing
> >  >>   system memory from the DSDT.
> >  >>
> >  >This is even worse. It requires some fixed address to be shared between
> >  >DSDT and Seabios (or alternatively Seabios will have to generate this
> >  >part of DSDT dynamically).
> >  >
> >
> >  Could easily be something in the F segment.
> >
> Yes, but then we will have two magic values (fwcfg index + address
> in F segment) instead of one (address of pci hot-plug controller).

The F segment address is internal to SeaBIOS; it isn't an external 
interface.

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

  reply	other threads:[~2010-12-13  9:10 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 [this message]
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
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=4D05E30E.20309@redhat.com \
    --to=avi@redhat.com \
    --cc=gleb@redhat.com \
    --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).