All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [patch 1/2] document QEMU<->ACPIBIOS PCI hotplug interface
Date: Mon, 17 Jan 2011 16:36:47 +0200	[thread overview]
Message-ID: <20110117143647.GA27919@redhat.com> (raw)
In-Reply-To: <20110111162353.910330983@redhat.com>

On Tue, Jan 11, 2011 at 02:20:38PM -0200, Marcelo Tosatti wrote:
> Document how QEMU communicates with ACPI BIOS for PCI hotplug.
> 
> Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>

This one seems to add whitespae errors:
/scm/qemu/.git/rebase-apply/patch:5: new blank line at EOF.
+
warning: 1 line adds whitespace errors.

> Index: qemu/docs/specs/acpi_pci_hotplug.txt
> ===================================================================
> --- /dev/null
> +++ qemu/docs/specs/acpi_pci_hotplug.txt
> @@ -0,0 +1,39 @@
> +QEMU<->ACPI BIOS PCI hotplug interface
> +--------------------------------------
> +
> +QEMU supports PCI hotplug via ACPI, for PCI bus 0. This document
> +describes the interface between QEMU and the ACPI BIOS.
> +
> +ACPI GPE block (IO ports 0xafe0-0xafe3, byte access):
> +-----------------------------------------
> +
> +Generic ACPI GPE block. Bit 1 (GPE.1) used to notify PCI hotplug/eject
> +event to ACPI BIOS, via SCI interrupt.
> +
> +PCI slot injection notification pending (IO port 0xae00-0xae03, 4-byte access):
> +---------------------------------------------------------------
> +Slot injection notification pending. One bit per slot.
> +
> +Read by ACPI BIOS GPE.1 handler to notify OS of injection
> +events.
> +
> +PCI slot removal notification (IO port 0xae04-0xae07, 4-byte access):
> +-----------------------------------------------------
> +Slot removal notification pending. One bit per slot.
> +
> +Read by ACPI BIOS GPE.1 handler to notify OS of removal
> +events.
> +
> +PCI device eject (IO port 0xae08-0xae0b, 4-byte access):
> +----------------------------------------
> +
> +Used by ACPI BIOS _EJ0 method to request device removal. One bit per slot.
> +Reads return 0.
> +
> +PCI removability status (IO port 0xae0c-0xae0f, 4-byte access):
> +-----------------------------------------------
> +
> +Used by ACPI BIOS _RMV method to indicate removability status to OS. One
> +bit per slot.
> +
> +
> 

  reply	other threads:[~2011-01-17 14:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-10 18:55 [Qemu-devel] [patch 0/2] [pci branch] configure pci slot removability through ACPI Marcelo Tosatti
2011-01-10 18:55 ` [Qemu-devel] [patch 1/2] document QEMU<->ACPIBIOS PCI hotplug interface Marcelo Tosatti
2011-01-10 18:55 ` [Qemu-devel] [patch 2/2] acpi_piix4: expose no_hotplug attribute via i/o port Marcelo Tosatti
2011-01-10 21:25   ` [Qemu-devel] " Michael S. Tsirkin
2011-01-11 16:20     ` [Qemu-devel] [patch 0/2] [pci branch] configure pci slot removability through ACPI (v2) Marcelo Tosatti
2011-01-11 16:20       ` [Qemu-devel] [patch 1/2] document QEMU<->ACPIBIOS PCI hotplug interface Marcelo Tosatti
2011-01-17 14:36         ` Michael S. Tsirkin [this message]
2011-01-11 16:20       ` [Qemu-devel] [patch 2/2] acpi_piix4: expose no_hotplug attribute via i/o port Marcelo Tosatti
2011-01-11 16:25     ` [Qemu-devel] " Marcelo Tosatti

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=20110117143647.GA27919@redhat.com \
    --to=mst@redhat.com \
    --cc=mtosatti@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.