All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@citrix.com>
To: "Shannon Zhao" <zhaoshenglong@huawei.com>,
	"Roger Pau Monné" <roger.pau@citrix.com>,
	xen-devel <xen-devel@lists.xen.org>,
	"Christoffer Dall" <christoffer.dall@linaro.org>,
	"Ian Campbell" <ian.campbell@citrix.com>,
	"Stefano Stabellini" <stefano.stabellini@eu.citrix.com>,
	"Stefano Stabellini" <stefano.stabellini@citrix.com>,
	"Jan Beulich" <jbeulich@suse.com>,
	"Parth Dixit" <parth.dixit@linaro.org>,
	andrew@fubar.geek.nz,
	"Boris Ostrovsky" <boris.ostrovsky@oracle.com>,
	"David Vrabel" <david.vrabel@citrix.com>
Cc: Hangaohuai <hangaohuai@huawei.com>,
	"Huangpeng (Peter)" <peter.huangpeng@huawei.com>,
	Shannon Zhao <shannon.zhao@linaro.org>
Subject: Re: Design doc of adding ACPI support for arm64 on Xen - version 4
Date: Wed, 19 Aug 2015 21:58:13 -0700	[thread overview]
Message-ID: <55D55E65.3030706@citrix.com> (raw)
In-Reply-To: <55D54483.5000103@huawei.com>



On 19/08/2015 20:07, Shannon Zhao wrote:
>> and I
>> don't think the domid field needs an explanation TBH.
>>
>>>
>>> Within the register, check if the device is newly added, then call
>>> hypercall XENMEM_add_to_physmap to map the mmio regions.
>>>
>>> For PCI bus device, it could reuse the existing PCI bus_notifier like
>>> X86.
>>
>> What is a PCI bus_notifier? I don't see any mention of bus_notifier in
>> Xen code.
>>
> I thought You konw what I mean here. If not, what should I do! Yeah, as
> you said, I will change the description.

Please remember that not everyone on the mailing list knows how work the 
internal of linux is working. The goal of the design doc is to explain 
to them in simple way what we are planning to do.

>
> But I want to say that the purpose of this document is to explain some
> important implementation details for ACPI support on ARM, which have
> some divergence before. I don't hope this doc to be official but I do
> hope this lets us reach an agreement on the approach before respinning
> the patches. If we focus on the words or description or even
> word-splitting, it doesn't help to make this move on!

I think you misunderstood what is the design doc. It's an high level
description about what will be implemented and official.

If people doesn't understand what you meant in the design doc, I don't 
see how they will be able to check that what you've implemented will be 
match what we agree. So the wording, description ... is really important.

Regards,

-- 
Julien Grall

  reply	other threads:[~2015-08-20  4:58 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-19 12:13 Design doc of adding ACPI support for arm64 on Xen - version 4 Shannon Zhao
2015-08-19 14:05 ` Jan Beulich
2015-08-19 18:37   ` Julien Grall
2015-08-20  9:22     ` Jan Beulich
2015-08-20  3:41   ` Shannon Zhao
2015-08-20  9:30     ` Jan Beulich
2015-08-20 12:56       ` Shannon Zhao
2015-08-20 14:06         ` Jan Beulich
2015-08-21  2:25           ` Shannon Zhao
2015-08-21 10:01             ` Jan Beulich
2015-08-27  0:37             ` Julien Grall
2015-08-27  7:52               ` Jan Beulich
2015-08-27 13:50                 ` Shannon Zhao
2015-08-27 14:13                   ` Jan Beulich
2015-08-27 14:21                     ` Shannon Zhao
2015-08-19 15:02 ` Roger Pau Monné
2015-08-20  3:07   ` Shannon Zhao
2015-08-20  4:58     ` Julien Grall [this message]
2015-08-20  8:20     ` Roger Pau Monné
2015-08-20 11:22       ` Shannon Zhao
2015-08-20 11:28         ` Roger Pau Monné
2015-08-20 12:13           ` Jan Beulich
2015-08-20 12:29           ` Shannon Zhao
2015-08-20 13:46             ` Roger Pau Monné
2015-08-20 14:09               ` Jan Beulich
2015-08-21  3:04               ` Shannon Zhao

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=55D55E65.3030706@citrix.com \
    --to=julien.grall@citrix.com \
    --cc=andrew@fubar.geek.nz \
    --cc=boris.ostrovsky@oracle.com \
    --cc=christoffer.dall@linaro.org \
    --cc=david.vrabel@citrix.com \
    --cc=hangaohuai@huawei.com \
    --cc=ian.campbell@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=parth.dixit@linaro.org \
    --cc=peter.huangpeng@huawei.com \
    --cc=roger.pau@citrix.com \
    --cc=shannon.zhao@linaro.org \
    --cc=stefano.stabellini@citrix.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xen.org \
    --cc=zhaoshenglong@huawei.com \
    /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.