Re: [PATCH 3/3] fs/core/vmcore: Move sev_active() reference to x86 arch code

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Halil Pasic <pasic@xxxxxxxxxxxxx>
Subject: Re: [PATCH 3/3] fs/core/vmcore: Move sev_active() reference to x86 arch code
From: Christoph Hellwig <hch@xxxxxx>
Date: Sat, 13 Jul 2019 10:08:29 +0200
Cc: Christoph Hellwig <hch@xxxxxx>, Thiago Jung Bauermann <bauerman@xxxxxxxxxxxxx>, x86@xxxxxxxxxx, iommu@xxxxxxxxxxxxxxxxxxxxxxxxxx, linux-fsdevel@xxxxxxxxxxxxxxx, linuxppc-dev@xxxxxxxxxxxxxxxx, linux-s390@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, Thomas Gleixner <tglx@xxxxxxxxxxxxx>, Ingo Molnar <mingo@xxxxxxxxxx>, Borislav Petkov <bp@xxxxxxxxx>, "H. Peter Anvin" <hpa@xxxxxxxxx>, Marek Szyprowski <m.szyprowski@xxxxxxxxxxx>, Robin Murphy <robin.murphy@xxxxxxx>, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>, Alexey Dobriyan <adobriyan@xxxxxxxxx>, Mike Anderson <andmike@xxxxxxxxxxxxx>, Ram Pai <linuxram@xxxxxxxxxx>
In-reply-to: <20190712174249.33b74535.pasic@linux.ibm.com>
User-agent: Mutt/1.5.17 (2007-11-01)

On Fri, Jul 12, 2019 at 05:42:49PM +0200, Halil Pasic wrote:
> 
> Will do! I guess I should do the patch against the for-next branch of the
> dma-mapping tree. But that branch does not have the s390 support patches (yet?).
> To fix it I need both e67a5ed1f86f and 64e1f0c531d1 "s390/mm: force
> swiotlb for protected virtualization" (Halil Pasic, 2018-09-13). Or
> should I wait for e67a5ed1f86f landing in mainline?

I've rebased the dma-mapping for-next branch to latest mainline as of
today that has both commits.

References:
- [PATCH 0/3] Remove x86-specific code from generic headers
  - From: Thiago Jung Bauermann
- [PATCH 3/3] fs/core/vmcore: Move sev_active() reference to x86 arch code
  - From: Thiago Jung Bauermann
- Re: [PATCH 3/3] fs/core/vmcore: Move sev_active() reference to x86 arch code
  - From: Halil Pasic
- Re: [PATCH 3/3] fs/core/vmcore: Move sev_active() reference to x86 arch code
  - From: Christoph Hellwig
- Re: [PATCH 3/3] fs/core/vmcore: Move sev_active() reference to x86 arch code
  - From: Halil Pasic
- Re: [PATCH 3/3] fs/core/vmcore: Move sev_active() reference to x86 arch code
  - From: Christoph Hellwig
- Re: [PATCH 3/3] fs/core/vmcore: Move sev_active() reference to x86 arch code
  - From: Halil Pasic

Prev by Date: Re: [PATCH 2/3] DMA mapping: Move SME handling to x86-specific files
Next by Date: Re: [PATCH] proc: Fix uninitialized byte read in get_mm_cmdline()
Previous by thread: Re: [PATCH 3/3] fs/core/vmcore: Move sev_active() reference to x86 arch code
Next by thread: Re: [PATCH 3/3] fs/core/vmcore: Move sev_active() reference to x86 arch code
Index(es):
- Date
- Thread

[Index of Archives] [Linux Ext4 Filesystem] [Union Filesystem] [Filesystem Testing] [Ceph Users] [Ecryptfs] [AutoFS] [Kernel Newbies] [Share Photos] [Security] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux Cachefs] [Reiser Filesystem] [Linux RAID] [Samba] [Device Mapper] [CEPH Development]