From: Christoph Hellwig <hch@lst.de>
To: Thiago Jung Bauermann <bauerman@linux.ibm.com>
Cc: linux-s390@vger.kernel.org, Mike Anderson <andmike@linux.ibm.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Robin Murphy <robin.murphy@arm.com>,
x86@kernel.org, Ram Pai <linuxram@us.ibm.com>,
linux-kernel@vger.kernel.org,
Alexey Dobriyan <adobriyan@gmail.com>,
Halil Pasic <pasic@linux.ibm.com>,
iommu@lists.linux-foundation.org, Ingo Molnar <mingo@redhat.com>,
Borislav Petkov <bp@alien8.de>,
Thomas Lendacky <Thomas.Lendacky@amd.com>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-fsdevel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
linuxppc-dev@lists.ozlabs.org, Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH 2/3] DMA mapping: Move SME handling to x86-specific files
Date: Sat, 13 Jul 2019 09:29:04 +0200 [thread overview]
Message-ID: <20190713072904.GC17589@lst.de> (raw)
In-Reply-To: <20190713044554.28719-3-bauerman@linux.ibm.com>
While this looks generally good to me, I think we want to split this
into three patches:
1) update the swiotlb printk
2) removing the dma-mapping check and printk
3) clean up the mem_encrypt.h interface.
_______________________________________________
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: Thiago Jung Bauermann <bauerman@linux.ibm.com>
Cc: x86@kernel.org, iommu@lists.linux-foundation.org,
linux-fsdevel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
"H. Peter Anvin" <hpa@zytor.com>, Christoph Hellwig <hch@lst.de>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Robin Murphy <robin.murphy@arm.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Alexey Dobriyan <adobriyan@gmail.com>,
Thomas Lendacky <Thomas.Lendacky@amd.com>,
Halil Pasic <pasic@linux.ibm.com>,
Mike Anderson <andmike@linux.ibm.com>,
Ram Pai <linuxram@us.ibm.com>
Subject: Re: [PATCH 2/3] DMA mapping: Move SME handling to x86-specific files
Date: Sat, 13 Jul 2019 09:29:04 +0200 [thread overview]
Message-ID: <20190713072904.GC17589@lst.de> (raw)
In-Reply-To: <20190713044554.28719-3-bauerman@linux.ibm.com>
While this looks generally good to me, I think we want to split this
into three patches:
1) update the swiotlb printk
2) removing the dma-mapping check and printk
3) clean up the mem_encrypt.h interface.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Thiago Jung Bauermann <bauerman@linux.ibm.com>
Cc: linux-s390@vger.kernel.org, Mike Anderson <andmike@linux.ibm.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Robin Murphy <robin.murphy@arm.com>,
x86@kernel.org, Ram Pai <linuxram@us.ibm.com>,
linux-kernel@vger.kernel.org,
Alexey Dobriyan <adobriyan@gmail.com>,
Halil Pasic <pasic@linux.ibm.com>,
iommu@lists.linux-foundation.org, Ingo Molnar <mingo@redhat.com>,
Borislav Petkov <bp@alien8.de>,
Thomas Lendacky <Thomas.Lendacky@amd.com>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-fsdevel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
linuxppc-dev@lists.ozlabs.org, Christoph Hellwig <hch@lst.de>,
Marek Szyprowski <m.szyprowski@samsung.com>
Subject: Re: [PATCH 2/3] DMA mapping: Move SME handling to x86-specific files
Date: Sat, 13 Jul 2019 09:29:04 +0200 [thread overview]
Message-ID: <20190713072904.GC17589@lst.de> (raw)
In-Reply-To: <20190713044554.28719-3-bauerman@linux.ibm.com>
While this looks generally good to me, I think we want to split this
into three patches:
1) update the swiotlb printk
2) removing the dma-mapping check and printk
3) clean up the mem_encrypt.h interface.
next prev parent reply other threads:[~2019-07-13 7:35 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-13 4:45 [PATCH 0/3] Remove x86-specific code from generic headers Thiago Jung Bauermann
2019-07-13 4:45 ` Thiago Jung Bauermann
2019-07-13 4:45 ` Thiago Jung Bauermann
2019-07-13 4:45 ` [PATCH 1/3] x86, s390: Move ARCH_HAS_MEM_ENCRYPT definition to arch/Kconfig Thiago Jung Bauermann
2019-07-13 4:45 ` Thiago Jung Bauermann
2019-07-13 4:45 ` [PATCH 1/3] x86,s390: " Thiago Jung Bauermann
2019-07-13 7:27 ` Christoph Hellwig
2019-07-13 7:27 ` Christoph Hellwig
2019-07-13 7:27 ` Christoph Hellwig
2019-07-15 15:23 ` [PATCH 1/3] x86, s390: " janani
2019-07-15 15:23 ` janani
2019-07-15 15:23 ` janani
2019-07-15 20:00 ` Thiago Jung Bauermann
2019-07-15 20:00 ` Thiago Jung Bauermann
2019-07-15 20:00 ` Thiago Jung Bauermann
2019-07-13 4:45 ` [PATCH 2/3] DMA mapping: Move SME handling to x86-specific files Thiago Jung Bauermann
2019-07-13 4:45 ` Thiago Jung Bauermann
2019-07-13 4:45 ` Thiago Jung Bauermann
2019-07-13 7:29 ` Christoph Hellwig [this message]
2019-07-13 7:29 ` Christoph Hellwig
2019-07-13 7:29 ` Christoph Hellwig
2019-07-13 4:45 ` [PATCH 3/3] fs/core/vmcore: Move sev_active() reference to x86 arch code Thiago Jung Bauermann
2019-07-13 4:45 ` Thiago Jung Bauermann
2019-07-13 4:45 ` Thiago Jung Bauermann
2019-07-13 5:08 ` [PATCH 0/3] Remove x86-specific code from generic headers Thiago Jung Bauermann
2019-07-13 5:08 ` Thiago Jung Bauermann
2019-07-13 5:08 ` Thiago Jung Bauermann
-- strict thread matches above, loose matches on Subject: below --
2019-07-12 5:36 Thiago Jung Bauermann
2019-07-12 5:36 ` [PATCH 2/3] DMA mapping: Move SME handling to x86-specific files Thiago Jung Bauermann
2019-07-12 5:36 ` Thiago Jung Bauermann
2019-07-12 5:36 ` Thiago Jung Bauermann
2019-07-12 7:13 ` Christoph Hellwig
2019-07-12 7:13 ` Christoph Hellwig
2019-07-12 7:13 ` Christoph Hellwig
2019-07-12 23:42 ` Thiago Jung Bauermann
2019-07-12 23:42 ` Thiago Jung Bauermann
2019-07-12 23:42 ` Thiago Jung Bauermann
2019-07-12 23:42 ` Thiago Jung Bauermann
2019-07-12 16:09 ` Thomas Gleixner
2019-07-12 16:09 ` Thomas Gleixner
2019-07-12 16:09 ` Thomas Gleixner
2019-07-18 19:47 ` Thiago Jung Bauermann
2019-07-18 19:47 ` Thiago Jung Bauermann
2019-07-18 19:47 ` Thiago Jung Bauermann
2019-07-19 9:05 ` kbuild test robot
2019-07-19 9:05 ` kbuild test robot
2019-07-19 9:05 ` kbuild test robot
2019-07-20 0:22 ` Thiago Jung Bauermann
2019-07-20 0:22 ` Thiago Jung Bauermann
2019-07-20 0:22 ` Thiago Jung Bauermann
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=20190713072904.GC17589@lst.de \
--to=hch@lst.de \
--cc=Thomas.Lendacky@amd.com \
--cc=adobriyan@gmail.com \
--cc=andmike@linux.ibm.com \
--cc=bauerman@linux.ibm.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=iommu@lists.linux-foundation.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=linuxram@us.ibm.com \
--cc=mingo@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=robin.murphy@arm.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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.