On Thu, Apr 05, 2012 at 12:04:44PM +0300, Michael S. Tsirkin wrote:
> On Thu, Apr 05, 2012 at 10:21:18AM +0200, Igor Mammedov wrote:
> > On 04/05/2012 07:51 AM, Alex Williamson wrote:
> > >This is never read. We can also derive bus from the write handler,
> > >making this more inline with the other callbacks. Note that
> > >pciej_write was actually called with (PCIBus *)dev->bus, which is
> > >cast as a void* allowing us to pretend it's a BusState*. Fix this
> > >so we don't depend on the BusState location within PCIBus.
> > >
> > >Signed-off-by: Alex Williamson<alex.william...@redhat.com>
> > >---
> > >
> > > docs/specs/acpi_pci_hotplug.txt | 2 +-
> > > hw/acpi_piix4.c | 14 ++++----------
> > > 2 files changed, 5 insertions(+), 11 deletions(-)
> > >
> > >diff --git a/docs/specs/acpi_pci_hotplug.txt
> > >b/docs/specs/acpi_pci_hotplug.txt
> > >index 1e2c8a2..1e61d19 100644
> > >--- a/docs/specs/acpi_pci_hotplug.txt
> > >+++ b/docs/specs/acpi_pci_hotplug.txt
> > >@@ -28,7 +28,7 @@ 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.
> > >+Read-only.
> > Write-only perhaps?
>
> Yes, let's also specify what happens in practice.
No we shouldn't.
> I think it is 'Guest should never read this register, in practice
> 0 is returned'.
>
In practice kitten die for each read. Unspecified behaviour is
unspecified.
--
Gleb.
