All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@arm.com>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: nd@arm.com, shankerd@qti.qualcomm.com, xen-devel@lists.xen.org
Subject: Re: [PATCH for-4.9] xen/arm: acpi: Map MMIO on fault in stage-2 page table for the hardware domain
Date: Fri, 31 Mar 2017 19:47:03 +0100	[thread overview]
Message-ID: <2ddbb383-1567-16fd-ecca-60da1b25dee6@arm.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1703311101220.2723@sstabellini-ThinkPad-X260>

Hi Stefano,

On 03/31/2017 07:01 PM, Stefano Stabellini wrote:
> On Fri, 31 Mar 2017, Julien Grall wrote:
>> On 30/03/17 20:54, Julien Grall wrote:
>>> On 30/03/2017 19:55, Stefano Stabellini wrote:
>>>> On Thu, 30 Mar 2017, Julien Grall wrote:
>>>>> On 30/03/17 19:37, Stefano Stabellini wrote:
>>>>>> On Thu, 30 Mar 2017, Julien Grall wrote:
>>>> Fair enough. Do you think there is any value in adding only one debug
>>>> warning, to say that we are mapping MMIOs on trap on this platform? But
>>>> today, it would basically be the same as saying "ACPI is enabled".
>>>
>>> I think we clearly need some documentation in tree to explain the design
>>> of Xen with ACPI and Device Tree. But this is lacking so far :/.
>>>
>>> I can have a go when I find some times.
>>
>> Just to make clear, I am planning to send that separately. Stefano, let me
>> know if it is fine for you.
>
> Yes, of course! But we still need the tiny is_hardware_domain fix.

I was hoping you to fix the is_hardware_domain :). Anyway, I will resend 
a new version on Monday with this change.

Cheers,

-- 
Julien Grall

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2017-03-31 18:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-30 12:43 [PATCH for-4.9] xen/arm: acpi: Map MMIO on fault in stage-2 page table for the hardware domain Julien Grall
2017-03-30 12:52 ` Shanker Donthineni
2017-03-30 12:58   ` Julien Grall
2017-03-30 13:15     ` Shanker Donthineni
2017-03-30 18:37 ` Stefano Stabellini
2017-03-30 18:45   ` Julien Grall
2017-03-30 18:55     ` Stefano Stabellini
2017-03-30 19:54       ` Julien Grall
2017-03-31 14:50         ` Julien Grall
2017-03-31 18:01           ` Stefano Stabellini
2017-03-31 18:47             ` Julien Grall [this message]
2017-03-31 18:50               ` Stefano Stabellini

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=2ddbb383-1567-16fd-ecca-60da1b25dee6@arm.com \
    --to=julien.grall@arm.com \
    --cc=nd@arm.com \
    --cc=shankerd@qti.qualcomm.com \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xen.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.