From: Christoph Hellwig <hch@lst.de>
To: Tom Lendacky <thomas.lendacky@amd.com>
Cc: Claire Chang <tientzu@chromium.org>,
Stefano Stabellini <sstabellini@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
mpe@ellerman.id.au, Joerg Roedel <joro@8bytes.org>,
Will Deacon <will@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
boris.ostrovsky@oracle.com, jgross@suse.com,
Christoph Hellwig <hch@lst.de>,
Marek Szyprowski <m.szyprowski@samsung.com>,
benh@kernel.crashing.org, paulus@samba.org,
"list@263.net:IOMMU DRIVERS" <iommu@lists.linux-foundation.org>,
Robin Murphy <robin.murphy@arm.com>,
grant.likely@arm.com, xypron.glpk@gmx.de,
Thierry Reding <treding@nvidia.com>,
mingo@kernel.org, bauerman@linux.ibm.com, peterz@infradead.org,
Greg KH <gregkh@linuxfoundation.org>,
Saravana Kannan <saravanak@google.com>,
"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
heikki.krogerus@linux.intel.com,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Randy Dunlap <rdunlap@infradead.org>,
Dan Williams <dan.j.williams@intel.com>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
linux-devicetree <devicetree@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>,
linuxppc-dev@lists.ozlabs.org, xen-devel@lists.xenproject.org,
Nicolas Boichat <drinkcat@chromium.org>,
Jim Quinlan <james.quinlan@broadcom.com>,
Tomasz Figa <tfiga@chromium.org>,
bskeggs@redhat.com, Bjorn Helgaas <bhelgaas@google.com>,
chris@chris-wilson.co.uk, Daniel Vetter <daniel@ffwll.ch>,
airlied@linux.ie, dri-devel@lists.freedesktop.org,
intel-gfx@lists.freedesktop.org, jani.nikula@linux.intel.com,
Jianxiong Gao <jxgao@google.com>,
joonas.lahtinen@linux.intel.com, linux-pci@vger.kernel.org,
maarten.lankhorst@linux.intel.com, matthew.auld@intel.com,
rodrigo.vivi@intel.com, thomas.hellstrom@linux.intel.com
Subject: Re: [PATCH v13 01/12] swiotlb: Refactor swiotlb init functions
Date: Fri, 18 Jun 2021 16:32:12 +0200 [thread overview]
Message-ID: <20210618143212.GA19284@lst.de> (raw)
In-Reply-To: <741a34cc-547c-984d-8af4-2f309880acfa@amd.com>
On Fri, Jun 18, 2021 at 09:09:17AM -0500, Tom Lendacky wrote:
> > swiotlb_init_with_tbl uses memblock_alloc to allocate the io_tlb_mem
> > and memblock_alloc[1] will do memset in memblock_alloc_try_nid[2], so
> > swiotlb_init_with_tbl is also good.
> > I'm happy to add the memset in swiotlb_init_io_tlb_mem if you think
> > it's clearer and safer.
>
> On x86, if the memset is done before set_memory_decrypted() and memory
> encryption is active, then the memory will look like ciphertext afterwards
> and not be zeroes. If zeroed memory is required, then a memset must be
> done after the set_memory_decrypted() calls.
Which should be fine - we don't care that the memory is cleared to 0,
just that it doesn't leak other data. Maybe a comment would be useful,
though,
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Tom Lendacky <thomas.lendacky@amd.com>
Cc: heikki.krogerus@linux.intel.com,
thomas.hellstrom@linux.intel.com, peterz@infradead.org,
joonas.lahtinen@linux.intel.com, dri-devel@lists.freedesktop.org,
chris@chris-wilson.co.uk, grant.likely@arm.com, paulus@samba.org,
Frank Rowand <frowand.list@gmail.com>,
mingo@kernel.org, Marek Szyprowski <m.szyprowski@samsung.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Saravana Kannan <saravanak@google.com>,
Joerg Roedel <joro@8bytes.org>,
"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
Christoph Hellwig <hch@lst.de>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
bskeggs@redhat.com, linux-pci@vger.kernel.org,
xen-devel@lists.xenproject.org,
Thierry Reding <treding@nvidia.com>,
intel-gfx@lists.freedesktop.org, matthew.auld@intel.com,
linux-devicetree <devicetree@vger.kernel.org>,
Jianxiong Gao <jxgao@google.com>, Daniel Vetter <daniel@ffwll.ch>,
Will Deacon <will@kernel.org>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
maarten.lankhorst@linux.intel.com, airlied@linux.ie,
Dan Williams <dan.j.williams@intel.com>,
linuxppc-dev@lists.ozlabs.org, jani.nikula@linux.intel.com,
Rob Herring <robh+dt@kernel.org>,
rodrigo.vivi@intel.com, Bjorn Helgaas <bhelgaas@google.com>,
Claire Chang <tientzu@chromium.org>,
boris.ostrovsky@oracle.com,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
jgross@suse.com, Nicolas Boichat <drinkcat@chromium.org>,
Greg KH <gregkh@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
lkml <linux-kernel@vger.kernel.org>,
Tomasz Figa <tfiga@chromium.org>,
"list@263.net:IOMMU DRIVERS" <iommu@lists.linux-foundation.org>,
Jim Quinlan <james.quinlan@broadcom.com>,
xypron.glpk@gmx.de, Robin Murphy <robin.murphy@arm.com>,
bauerman@linux.ibm.com
Subject: Re: [PATCH v13 01/12] swiotlb: Refactor swiotlb init functions
Date: Fri, 18 Jun 2021 16:32:12 +0200 [thread overview]
Message-ID: <20210618143212.GA19284@lst.de> (raw)
In-Reply-To: <741a34cc-547c-984d-8af4-2f309880acfa@amd.com>
On Fri, Jun 18, 2021 at 09:09:17AM -0500, Tom Lendacky wrote:
> > swiotlb_init_with_tbl uses memblock_alloc to allocate the io_tlb_mem
> > and memblock_alloc[1] will do memset in memblock_alloc_try_nid[2], so
> > swiotlb_init_with_tbl is also good.
> > I'm happy to add the memset in swiotlb_init_io_tlb_mem if you think
> > it's clearer and safer.
>
> On x86, if the memset is done before set_memory_decrypted() and memory
> encryption is active, then the memory will look like ciphertext afterwards
> and not be zeroes. If zeroed memory is required, then a memset must be
> done after the set_memory_decrypted() calls.
Which should be fine - we don't care that the memory is cleared to 0,
just that it doesn't leak other data. Maybe a comment would be useful,
though,
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Tom Lendacky <thomas.lendacky@amd.com>
Cc: heikki.krogerus@linux.intel.com,
thomas.hellstrom@linux.intel.com, peterz@infradead.org,
benh@kernel.crashing.org, joonas.lahtinen@linux.intel.com,
dri-devel@lists.freedesktop.org, chris@chris-wilson.co.uk,
grant.likely@arm.com, paulus@samba.org,
Frank Rowand <frowand.list@gmail.com>,
mingo@kernel.org, Stefano Stabellini <sstabellini@kernel.org>,
Saravana Kannan <saravanak@google.com>,
mpe@ellerman.id.au,
"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
Christoph Hellwig <hch@lst.de>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
bskeggs@redhat.com, linux-pci@vger.kernel.org,
xen-devel@lists.xenproject.org,
Thierry Reding <treding@nvidia.com>,
intel-gfx@lists.freedesktop.org, matthew.auld@intel.com,
linux-devicetree <devicetree@vger.kernel.org>,
Jianxiong Gao <jxgao@google.com>, Daniel Vetter <daniel@ffwll.ch>,
Will Deacon <will@kernel.org>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
maarten.lankhorst@linux.intel.com, airlied@linux.ie,
Dan Williams <dan.j.williams@intel.com>,
linuxppc-dev@lists.ozlabs.org, jani.nikula@linux.intel.com,
Rob Herring <robh+dt@kernel.org>,
rodrigo.vivi@intel.com, Bjorn Helgaas <bhelgaas@google.com>,
Claire Chang <tientzu@chromium.org>,
boris.ostrovsky@oracle.com,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
jgross@suse.com, Nicolas Boichat <drinkcat@chromium.org>,
Greg KH <gregkh@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
lkml <linux-kernel@vger.kernel.org>,
"list@263.net:IOMMU DRIVERS" <iommu@lists.linux-foundation.org>,
Jim Quinlan <james.quinlan@broadcom.com>,
xypron.glpk@gmx.de, Robin Murphy <robin.murphy@arm.com>,
bauerman@linux.ibm.com
Subject: Re: [PATCH v13 01/12] swiotlb: Refactor swiotlb init functions
Date: Fri, 18 Jun 2021 16:32:12 +0200 [thread overview]
Message-ID: <20210618143212.GA19284@lst.de> (raw)
In-Reply-To: <741a34cc-547c-984d-8af4-2f309880acfa@amd.com>
On Fri, Jun 18, 2021 at 09:09:17AM -0500, Tom Lendacky wrote:
> > swiotlb_init_with_tbl uses memblock_alloc to allocate the io_tlb_mem
> > and memblock_alloc[1] will do memset in memblock_alloc_try_nid[2], so
> > swiotlb_init_with_tbl is also good.
> > I'm happy to add the memset in swiotlb_init_io_tlb_mem if you think
> > it's clearer and safer.
>
> On x86, if the memset is done before set_memory_decrypted() and memory
> encryption is active, then the memory will look like ciphertext afterwards
> and not be zeroes. If zeroed memory is required, then a memset must be
> done after the set_memory_decrypted() calls.
Which should be fine - we don't care that the memory is cleared to 0,
just that it doesn't leak other data. Maybe a comment would be useful,
though,
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Tom Lendacky <thomas.lendacky@amd.com>
Cc: heikki.krogerus@linux.intel.com,
thomas.hellstrom@linux.intel.com, peterz@infradead.org,
benh@kernel.crashing.org, dri-devel@lists.freedesktop.org,
chris@chris-wilson.co.uk, grant.likely@arm.com, paulus@samba.org,
Frank Rowand <frowand.list@gmail.com>,
mingo@kernel.org, Marek Szyprowski <m.szyprowski@samsung.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Saravana Kannan <saravanak@google.com>,
mpe@ellerman.id.au, Joerg Roedel <joro@8bytes.org>,
"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
Christoph Hellwig <hch@lst.de>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
bskeggs@redhat.com, linux-pci@vger.kernel.org,
xen-devel@lists.xenproject.org,
Thierry Reding <treding@nvidia.com>,
intel-gfx@lists.freedesktop.org, matthew.auld@intel.com,
linux-devicetree <devicetree@vger.kernel.org>,
Jianxiong Gao <jxgao@google.com>, Will Deacon <will@kernel.org>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
airlied@linux.ie, Dan Williams <dan.j.williams@intel.com>,
linuxppc-dev@lists.ozlabs.org, Rob Herring <robh+dt@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
Claire Chang <tientzu@chromium.org>,
boris.ostrovsky@oracle.com,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
jgross@suse.com, Nicolas Boichat <drinkcat@chromium.org>,
Greg KH <gregkh@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
lkml <linux-kernel@vger.kernel.org>,
Tomasz Figa <tfiga@chromium.org>,
"list@263.net:IOMMU DRIVERS" <iommu@lists.linux-foundation.org>,
Jim Quinlan <james.quinlan@broadcom.com>,
xypron.glpk@gmx.de, Robin Murphy <robin.murphy@arm.com>,
bauerman@linux.ibm.com
Subject: Re: [Intel-gfx] [PATCH v13 01/12] swiotlb: Refactor swiotlb init functions
Date: Fri, 18 Jun 2021 16:32:12 +0200 [thread overview]
Message-ID: <20210618143212.GA19284@lst.de> (raw)
In-Reply-To: <741a34cc-547c-984d-8af4-2f309880acfa@amd.com>
On Fri, Jun 18, 2021 at 09:09:17AM -0500, Tom Lendacky wrote:
> > swiotlb_init_with_tbl uses memblock_alloc to allocate the io_tlb_mem
> > and memblock_alloc[1] will do memset in memblock_alloc_try_nid[2], so
> > swiotlb_init_with_tbl is also good.
> > I'm happy to add the memset in swiotlb_init_io_tlb_mem if you think
> > it's clearer and safer.
>
> On x86, if the memset is done before set_memory_decrypted() and memory
> encryption is active, then the memory will look like ciphertext afterwards
> and not be zeroes. If zeroed memory is required, then a memset must be
> done after the set_memory_decrypted() calls.
Which should be fine - we don't care that the memory is cleared to 0,
just that it doesn't leak other data. Maybe a comment would be useful,
though,
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2021-06-18 14:32 UTC|newest]
Thread overview: 139+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-17 6:26 [PATCH v13 00/12] Restricted DMA Claire Chang
2021-06-17 6:26 ` [Intel-gfx] " Claire Chang
2021-06-17 6:26 ` Claire Chang
2021-06-17 6:26 ` Claire Chang
2021-06-17 6:26 ` Claire Chang
2021-06-17 6:26 ` [PATCH v13 01/12] swiotlb: Refactor swiotlb init functions Claire Chang
2021-06-17 6:26 ` [Intel-gfx] " Claire Chang
2021-06-17 6:26 ` Claire Chang
2021-06-17 6:26 ` Claire Chang
2021-06-17 6:26 ` Claire Chang
2021-06-17 23:30 ` Stefano Stabellini
2021-06-17 23:30 ` Stefano Stabellini
2021-06-17 23:30 ` [Intel-gfx] " Stefano Stabellini
2021-06-17 23:30 ` Stefano Stabellini
2021-06-17 23:30 ` Stefano Stabellini
2021-06-17 23:30 ` Stefano Stabellini
2021-06-18 6:25 ` Claire Chang
2021-06-18 6:25 ` Claire Chang
2021-06-18 6:25 ` [Intel-gfx] " Claire Chang
2021-06-18 6:25 ` Claire Chang
2021-06-18 6:25 ` Claire Chang
2021-06-18 6:25 ` Claire Chang
2021-06-18 14:09 ` Tom Lendacky
2021-06-18 14:09 ` [Intel-gfx] " Tom Lendacky
2021-06-18 14:09 ` Tom Lendacky
2021-06-18 14:09 ` Tom Lendacky via iommu
2021-06-18 14:09 ` Tom Lendacky
2021-06-18 14:32 ` Christoph Hellwig [this message]
2021-06-18 14:32 ` [Intel-gfx] " Christoph Hellwig
2021-06-18 14:32 ` Christoph Hellwig
2021-06-18 14:32 ` Christoph Hellwig
2021-06-21 17:59 ` Stefano Stabellini
2021-06-21 17:59 ` Stefano Stabellini
2021-06-21 17:59 ` [Intel-gfx] " Stefano Stabellini
2021-06-21 17:59 ` Stefano Stabellini
2021-06-21 17:59 ` Stefano Stabellini
2021-06-21 17:59 ` Stefano Stabellini
2021-06-21 20:19 ` Christoph Hellwig
2021-06-21 20:19 ` [Intel-gfx] " Christoph Hellwig
2021-06-21 20:19 ` Christoph Hellwig
2021-06-21 20:19 ` Christoph Hellwig
2021-06-17 6:26 ` [PATCH v13 02/12] swiotlb: Refactor swiotlb_create_debugfs Claire Chang
2021-06-17 6:26 ` [Intel-gfx] " Claire Chang
2021-06-17 6:26 ` Claire Chang
2021-06-17 6:26 ` Claire Chang
2021-06-17 6:26 ` Claire Chang
2021-06-17 6:26 ` [PATCH v13 03/12] swiotlb: Set dev->dma_io_tlb_mem to the swiotlb pool used Claire Chang
2021-06-17 6:26 ` [Intel-gfx] " Claire Chang
2021-06-17 6:26 ` Claire Chang
2021-06-17 6:26 ` Claire Chang
2021-06-17 6:26 ` Claire Chang
2021-06-17 23:30 ` Stefano Stabellini
2021-06-17 23:30 ` Stefano Stabellini
2021-06-17 23:30 ` [Intel-gfx] " Stefano Stabellini
2021-06-17 23:30 ` Stefano Stabellini
2021-06-17 23:30 ` Stefano Stabellini
2021-06-17 23:30 ` Stefano Stabellini
2021-06-17 6:26 ` [PATCH v13 04/12] swiotlb: Update is_swiotlb_buffer to add a struct device argument Claire Chang
2021-06-17 6:26 ` [Intel-gfx] " Claire Chang
2021-06-17 6:26 ` Claire Chang
2021-06-17 6:26 ` Claire Chang
2021-06-17 6:26 ` Claire Chang
2021-06-17 23:30 ` Stefano Stabellini
2021-06-17 23:30 ` Stefano Stabellini
2021-06-17 23:30 ` [Intel-gfx] " Stefano Stabellini
2021-06-17 23:30 ` Stefano Stabellini
2021-06-17 23:30 ` Stefano Stabellini
2021-06-17 23:30 ` Stefano Stabellini
2021-06-17 6:26 ` [PATCH v13 05/12] swiotlb: Update is_swiotlb_active " Claire Chang
2021-06-17 6:26 ` [Intel-gfx] " Claire Chang
2021-06-17 6:26 ` Claire Chang
2021-06-17 6:26 ` Claire Chang
2021-06-17 6:26 ` Claire Chang
2021-06-17 23:30 ` Stefano Stabellini
2021-06-17 23:30 ` Stefano Stabellini
2021-06-17 23:30 ` [Intel-gfx] " Stefano Stabellini
2021-06-17 23:30 ` Stefano Stabellini
2021-06-17 23:30 ` Stefano Stabellini
2021-06-17 23:30 ` Stefano Stabellini
2021-06-17 6:26 ` [PATCH v13 06/12] swiotlb: Use is_swiotlb_force_bounce for swiotlb data bouncing Claire Chang
2021-06-17 6:26 ` [Intel-gfx] " Claire Chang
2021-06-17 6:26 ` Claire Chang
2021-06-17 6:26 ` Claire Chang
2021-06-17 6:26 ` Claire Chang
2021-06-17 23:31 ` Stefano Stabellini
2021-06-17 23:31 ` Stefano Stabellini
2021-06-17 23:31 ` [Intel-gfx] " Stefano Stabellini
2021-06-17 23:31 ` Stefano Stabellini
2021-06-17 23:31 ` Stefano Stabellini
2021-06-17 23:31 ` Stefano Stabellini
2021-06-17 6:26 ` [PATCH v13 07/12] swiotlb: Move alloc_size to swiotlb_find_slots Claire Chang
2021-06-17 6:26 ` [Intel-gfx] " Claire Chang
2021-06-17 6:26 ` Claire Chang
2021-06-17 6:26 ` Claire Chang
2021-06-17 6:26 ` Claire Chang
2021-06-17 6:26 ` [PATCH v13 08/12] swiotlb: Refactor swiotlb_tbl_unmap_single Claire Chang
2021-06-17 6:26 ` [Intel-gfx] " Claire Chang
2021-06-17 6:26 ` Claire Chang
2021-06-17 6:26 ` Claire Chang
2021-06-17 6:26 ` Claire Chang
2021-06-17 6:26 ` [PATCH v13 09/12] swiotlb: Add restricted DMA alloc/free support Claire Chang
2021-06-17 6:26 ` [Intel-gfx] " Claire Chang
2021-06-17 6:26 ` Claire Chang
2021-06-17 6:26 ` Claire Chang
2021-06-17 6:26 ` Claire Chang
2021-06-17 23:31 ` Stefano Stabellini
2021-06-17 23:31 ` Stefano Stabellini
2021-06-17 23:31 ` [Intel-gfx] " Stefano Stabellini
2021-06-17 23:31 ` Stefano Stabellini
2021-06-17 23:31 ` Stefano Stabellini
2021-06-17 23:31 ` Stefano Stabellini
2021-06-17 6:26 ` [PATCH v13 10/12] swiotlb: Add restricted DMA pool initialization Claire Chang
2021-06-17 6:26 ` [Intel-gfx] " Claire Chang
2021-06-17 6:26 ` Claire Chang
2021-06-17 6:26 ` Claire Chang
2021-06-17 6:26 ` Claire Chang
2021-06-17 6:26 ` [PATCH v13 11/12] dt-bindings: of: Add restricted DMA pool Claire Chang
2021-06-17 6:26 ` [Intel-gfx] " Claire Chang
2021-06-17 6:26 ` Claire Chang
2021-06-17 6:26 ` Claire Chang
2021-06-17 6:26 ` Claire Chang
2021-06-17 6:26 ` [PATCH v13 12/12] of: Add plumbing for " Claire Chang
2021-06-17 6:26 ` [Intel-gfx] " Claire Chang
2021-06-17 6:26 ` Claire Chang
2021-06-17 6:26 ` Claire Chang
2021-06-17 6:26 ` Claire Chang
2021-06-17 6:32 ` [PATCH v13 00/12] Restricted DMA Claire Chang
2021-06-17 6:32 ` Claire Chang
2021-06-17 6:32 ` [Intel-gfx] " Claire Chang
2021-06-17 6:32 ` Claire Chang
2021-06-17 6:32 ` Claire Chang
2021-06-17 6:32 ` Claire Chang
2021-06-19 3:43 ` Claire Chang
2021-06-19 3:43 ` Claire Chang
2021-06-19 3:43 ` [Intel-gfx] " Claire Chang
2021-06-19 3:43 ` Claire Chang
2021-06-19 3:43 ` Claire Chang
2021-06-19 3:43 ` Claire Chang
2021-06-17 6:33 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for " Patchwork
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=20210618143212.GA19284@lst.de \
--to=hch@lst.de \
--cc=airlied@linux.ie \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bauerman@linux.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=bgolaszewski@baylibre.com \
--cc=bhelgaas@google.com \
--cc=boris.ostrovsky@oracle.com \
--cc=bskeggs@redhat.com \
--cc=chris@chris-wilson.co.uk \
--cc=dan.j.williams@intel.com \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=drinkcat@chromium.org \
--cc=frowand.list@gmail.com \
--cc=grant.likely@arm.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=iommu@lists.linux-foundation.org \
--cc=james.quinlan@broadcom.com \
--cc=jani.nikula@linux.intel.com \
--cc=jgross@suse.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=joro@8bytes.org \
--cc=jxgao@google.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=m.szyprowski@samsung.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=matthew.auld@intel.com \
--cc=mingo@kernel.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rdunlap@infradead.org \
--cc=robh+dt@kernel.org \
--cc=robin.murphy@arm.com \
--cc=rodrigo.vivi@intel.com \
--cc=saravanak@google.com \
--cc=sstabellini@kernel.org \
--cc=tfiga@chromium.org \
--cc=thomas.hellstrom@linux.intel.com \
--cc=thomas.lendacky@amd.com \
--cc=tientzu@chromium.org \
--cc=treding@nvidia.com \
--cc=will@kernel.org \
--cc=xen-devel@lists.xenproject.org \
--cc=xypron.glpk@gmx.de \
/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.