From: Shannon Zhao <shannon.zhao@linaro.org>
To: G Gregory <graeme.gregory@linaro.org>,
Leif Lindholm <leif.lindholm@linaro.org>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Andrew Jones <drjones@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Al Stone <al.stone@linaro.org>
Subject: Re: [Qemu-devel] [PATCH] hw/arm/virt-acpi-build: drop _ADR entry from SPCR
Date: Thu, 20 Aug 2015 19:09:57 +0800 [thread overview]
Message-ID: <55D5B585.6070307@linaro.org> (raw)
In-Reply-To: <CAGCh1+=uq3N287aoOFgiNiwGXScQ-j4eR821AF9WLOF59cZsCQ@mail.gmail.com>
On 2015/8/20 18:48, G Gregory wrote:
> On 20 August 2015 at 11:18, Leif Lindholm <leif.lindholm@linaro.org> wrote:
>> On Thu, Aug 20, 2015 at 01:24:39AM +0100, Peter Maydell wrote:
>>> On 6 August 2015 at 14:25, Andrew Jones <drjones@redhat.com> wrote:
>>>> On Thu, Aug 06, 2015 at 01:55:14PM +0100, Leif Lindholm wrote:
>>>>> On Thu, Aug 06, 2015 at 02:28:03PM +0200, Andrew Jones wrote:
>>>>>> In the least I wouldn't want to get burned twice, so I'd prefer to
>>>>>> see the SPCR code actually get into Linux first this time. That
>>>>>> would also allow us to point at something when we start breaking
>>>>>> guests.
>>>>>
>>>>> So, if that's the way it has to be, that's the way it has to be.
>>>>> I'd just prefer not having different pieces of firmware validating
>>>>> different software behaviours for the same thing.
>>>>
>>>> Yeah, now it's messy. I'm actually OK with this QEMU patch, with regard
>>>> to the downstream stuff that I'm involved with, but other downstreams
>>>> may not be so flexible... We need Peter to chime in with his opinion,
>>>> CCed.
>>>
>>> Could somebody who understands ACPI and the ramifications
>>> here let me know if I should apply this patch, please?
>>> (since we're now post-2.4)
>>
>> I presume my opinion is clear, but I'm cc:ing some of the Linaro ACPI
>> team.
>>
>> Graeme, Al - the patch in question is:
>> https://www.mail-archive.com/qemu-devel%40nongnu.org/msg314356.html
>>
> Using _ADR for a non enumerable bus is undefined behaviour in the ACPI
> specification.
>
> How it is used in Redhats SPCR patch is IMO wrong becuase there is no
> guarantee that _ADR will be defined for any MMIO device in DSDT.
>
> I believe QEMU should not follow this just to make a non upstreamed
> Redhat patch work.
>
Yeah, but when will the right kernel patch be upstreamed? Do you have a
plan for upstreaming it? Or it's on the list already?
As said before, we can apply this patch after the kernel patch upstreamed.
Thanks,
--
Shannon
next prev parent reply other threads:[~2015-08-20 11:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-06 11:24 [Qemu-devel] [PATCH] hw/arm/virt-acpi-build: drop _ADR entry from SPCR Leif Lindholm
2015-08-06 12:28 ` Andrew Jones
2015-08-06 12:55 ` Leif Lindholm
2015-08-06 13:25 ` Andrew Jones
2015-08-07 7:17 ` Peter Maydell
2015-08-20 0:24 ` Peter Maydell
2015-08-20 1:17 ` Shannon Zhao
2015-08-20 10:18 ` Leif Lindholm
2015-08-20 10:48 ` G Gregory
2015-08-20 11:09 ` Shannon Zhao [this message]
2015-08-20 11:21 ` Leif Lindholm
2015-08-20 21:54 ` Andrew Jones
2015-09-04 17:14 ` Peter Maydell
2015-08-06 13:19 ` Shannon Zhao
2015-08-06 14:00 ` Peter Maydell
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=55D5B585.6070307@linaro.org \
--to=shannon.zhao@linaro.org \
--cc=al.stone@linaro.org \
--cc=drjones@redhat.com \
--cc=graeme.gregory@linaro.org \
--cc=leif.lindholm@linaro.org \
--cc=peter.maydell@linaro.org \
--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 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).