| Message ID | 20190807002311.9906-6-sstabellini@kernel.org (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
| Series | [v4,1/6] xen/arm: introduce p2m_is_mmio | expand |
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 > --- > 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 > >
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 >> >
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 Status: Supported, not security supported
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 --- SUPPORT.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)