All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@arm.com>
To: Stefano Stabellini <sstabellini@kernel.org>,
	xen-devel@lists.xenproject.org
Cc: Stefano Stabellini <stefanos@xilinx.com>, WeiLiu <wl@xen.org>,
	konrad.wilk@oracle.com,
	George Dunlap <george.dunlap@eu.citrix.com>,
	andrew.cooper3@citrix.com, tim@xen.org, JBeulich@suse.com,
	ian.jackson@eu.citrix.com
Subject: Re: [Xen-devel] [PATCH v4 6/6] xen/arm: clarify the support status of iomem configurations
Date: Wed, 7 Aug 2019 10:16:26 +0100	[thread overview]
Message-ID: <18fa3016-573c-2f87-4a35-ed27bb7cb4a0@arm.com> (raw)
In-Reply-To: <887f853a-d715-b33e-8c76-4280cdbfbab1@arm.com>

Hi,

On 07/08/2019 10:08, Julien Grall wrote:
> Hi,
> 
> On 07/08/2019 01:23, Stefano Stabellini wrote:
>> iomem settings fall under the broader category of "Non-PCI device
>> passthrough": they are not security supported. Make it clearer.
>>
>> Signed-off-by: Stefano Stabellini <stefanos@xilinx.com>
>> CC: tim@xen.org
>> CC: konrad.wilk@oracle.com
>> CC: Julien Grall <julien.grall@arm.com>
>> CC: JBeulich@suse.com
>> CC: andrew.cooper3@citrix.com
>> CC: ian.jackson@eu.citrix.com
>> CC: wei.liu2@citrix.com

I just realized after sending the e-mail that the list of CC is smaller than it 
should and Wei's e-mail is incorrect. On the other e-mails, you forgot to CC 
Volodymyr as Arm reviewer.

I am pretty sure I already pointed that out in the past... We have tools in 
place to find out the maintainers to CC and add them (see 
scripts/add_maintainers.pl). So there are no need to do this manually anymore.

>> ---
>>   SUPPORT.md | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/SUPPORT.md b/SUPPORT.md
>> index 375473a456..bc6fb58e04 100644
>> --- a/SUPPORT.md
>> +++ b/SUPPORT.md
>> @@ -639,7 +639,7 @@ to be used in addition to QEMU.
>>       Status: Experimental
>> -### ARM/Non-PCI device passthrough
>> +### ARM/Non-PCI device passthrough and other iomem configurations
> 
> I don't understand the new title. What are the other use case of IOMEM 
> configurations?
> 
> Cheers,
> 
>>       Status: Supported, not security supported
>>
> 

-- 
Julien Grall

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

      reply	other threads:[~2019-08-07  9:16 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-07  0:23 [Xen-devel] [PATCH v4 0/6] iomem memory policy Stefano Stabellini
2019-08-07  0:23 ` [Xen-devel] [PATCH v4 1/6] xen/arm: introduce p2m_is_mmio Stefano Stabellini
2019-08-09 10:05   ` Julien Grall
2019-08-07  0:23 ` [Xen-devel] [PATCH v4 2/6] xen: add a p2mt parameter to map_mmio_regions Stefano Stabellini
2019-08-09 10:23   ` Julien Grall
2019-08-09 10:37     ` Jan Beulich
2019-08-09 10:51       ` Julien Grall
2019-08-09 11:07         ` Jan Beulich
2019-08-09 11:10   ` Jan Beulich
2019-08-07  0:23 ` [Xen-devel] [PATCH v4 3/6] xen: extend XEN_DOMCTL_memory_mapping to handle memory policy Stefano Stabellini
2019-08-09 11:25   ` Jan Beulich
2019-08-09 17:25   ` Julien Grall
2019-08-07  0:23 ` [Xen-devel] [PATCH v4 4/6] libxc: introduce xc_domain_mem_map_policy Stefano Stabellini
2019-08-07  0:23 ` [Xen-devel] [PATCH v4 5/6] libxl/xl: add memory policy option to iomem Stefano Stabellini
2019-08-09 17:23   ` Julien Grall
2019-08-07  0:23 ` [Xen-devel] [PATCH v4 6/6] xen/arm: clarify the support status of iomem configurations Stefano Stabellini
2019-08-07  9:08   ` Julien Grall
2019-08-07  9:16     ` Julien Grall [this message]

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=18fa3016-573c-2f87-4a35-ed27bb7cb4a0@arm.com \
    --to=julien.grall@arm.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=george.dunlap@eu.citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=konrad.wilk@oracle.com \
    --cc=sstabellini@kernel.org \
    --cc=stefanos@xilinx.com \
    --cc=tim@xen.org \
    --cc=wl@xen.org \
    --cc=xen-devel@lists.xenproject.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.