All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Apfelbaum <marcel@redhat.com>
To: "Mark Cave-Ayland" <mark.cave-ayland@ilande.co.uk>,
	"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
	atar4qemu@gmail.com, "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] sun4u: implement power device
Date: Wed, 17 Jan 2018 16:25:04 +0200	[thread overview]
Message-ID: <d9ab0369-774b-4e2b-ba6d-18685ca4e00a@redhat.com> (raw)
In-Reply-To: <f59cf77f-e796-19a7-148f-d91fbd09b9b8@ilande.co.uk>

On 16/01/2018 22:05, Mark Cave-Ayland wrote:
> On 16/01/18 14:23, Marcel Apfelbaum wrote:
> 
>> Hi Philippe,
>>
>> On 16/01/2018 2:54, Philippe Mathieu-Daudé wrote:
>>> CC'ing PCI maintainers.
>>>
>>> Hi Mark,
>>>
>>> On 01/15/2018 05:58 PM, Mark Cave-Ayland wrote:
>>>> This inbuilt device contains a single 4-byte register, of which bit 24 is used
>>>> to power down the machine on a real Ultra 5.
>>>>
>>>> The power device exists at offset 0x724000 on a real machine, but due to the
>>>> current configuration of the BARs in QEMU it must be located lower in PCI IO
>>>> space.
>>> Is is some issue in pci_bar_address()?
>>>
>>
>> The QEMU IO layout:
>>
>>      /*
>>       * QEMU I/O address space usage:
>>       *   0000 - 0fff    legacy isa, pci config, pci root bus, ...
>>       *   1000 - 9fff    free
>>       *   a000 - afff    hotplug (cpu, pci via acpi, i440fx/piix only)
>>       *   b000 - bfff    power management (PORT_ACPI_PM_BASE)
>>       *                  [ qemu 1.4+ implements pci config registers
>>       *                    properly so guests can place the registers
>>       *                    where they want, on older versions its fixed ]
>>       *   c000 - ffff    free, traditionally used for pci io
>>       */
>>
>> As you can see we don't have IO address space over ffff.
> 
> Well that's not actually quite true - we use a separate ebus address space for the onboard devices (and that does have 
> 32-bit PCI IO accesses enabled), but the issue here is one of the sun4u PCI host/onboard device configuration rather 
> than anything to do with QEMU.
> 

Got it, thanks (the above is probably true only for x86 machines)
Marcel

> 
> ATB,
> 
> Mark.

  reply	other threads:[~2018-01-17 14:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-15 20:58 [Qemu-devel] [PATCH] sun4u: implement power device Mark Cave-Ayland
2018-01-16  0:54 ` Philippe Mathieu-Daudé
2018-01-16 14:23   ` Marcel Apfelbaum
2018-01-16 20:05     ` Mark Cave-Ayland
2018-01-17 14:25       ` Marcel Apfelbaum [this message]
2018-01-16 20:03   ` Mark Cave-Ayland
2018-01-20 20:10 ` Artyom Tarasenko
2018-01-21  9:14   ` Mark Cave-Ayland

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=d9ab0369-774b-4e2b-ba6d-18685ca4e00a@redhat.com \
    --to=marcel@redhat.com \
    --cc=atar4qemu@gmail.com \
    --cc=f4bug@amsat.org \
    --cc=mark.cave-ayland@ilande.co.uk \
    --cc=mst@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.