All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thiago Jung Bauermann <bauerman@linux.ibm.com>
To: Thomas Gleixner <tglx@linutronix.de>
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,
	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>,
	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: Thu, 18 Jul 2019 16:47:09 -0300	[thread overview]
Message-ID: <878ssv3z2a.fsf@morokweng.localdomain> (raw)
In-Reply-To: <alpine.DEB.2.21.1907121806160.1788@nanos.tec.linutronix.de>


Thomas Gleixner <tglx@linutronix.de> writes:

> On Fri, 12 Jul 2019, Thiago Jung Bauermann wrote:
>> diff --git a/include/linux/mem_encrypt.h b/include/linux/mem_encrypt.h
>> index b310a9c18113..f2e399fb626b 100644
>> --- a/include/linux/mem_encrypt.h
>> +++ b/include/linux/mem_encrypt.h
>> @@ -21,23 +21,11 @@
>>  
>>  #else	/* !CONFIG_ARCH_HAS_MEM_ENCRYPT */
>>  
>> -#define sme_me_mask	0ULL
>> -
>> -static inline bool sme_active(void) { return false; }
>>  static inline bool sev_active(void) { return false; }
>
> You want to move out sev_active as well, the only relevant thing is
> mem_encrypt_active(). Everything SME/SEV is an architecture detail.

I'm sure you saw it. I addressed sev_active in a separate patch.

Thanks for reviewing this series!

>> +static inline bool mem_encrypt_active(void) { return false; }
>
> Thanks,
>
> 	tglx


-- 
Thiago Jung Bauermann
IBM Linux Technology Center


WARNING: multiple messages have this Message-ID (diff)
From: Thiago Jung Bauermann <bauerman@linux.ibm.com>
To: Thomas Gleixner <tglx@linutronix.de>
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>, "H. Peter Anvin" <hpa@zytor.com>,
	linux-fsdevel@vger.kernel.org, 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: Thu, 18 Jul 2019 16:47:09 -0300	[thread overview]
Message-ID: <878ssv3z2a.fsf@morokweng.localdomain> (raw)
In-Reply-To: <alpine.DEB.2.21.1907121806160.1788@nanos.tec.linutronix.de>


Thomas Gleixner <tglx@linutronix.de> writes:

> On Fri, 12 Jul 2019, Thiago Jung Bauermann wrote:
>> diff --git a/include/linux/mem_encrypt.h b/include/linux/mem_encrypt.h
>> index b310a9c18113..f2e399fb626b 100644
>> --- a/include/linux/mem_encrypt.h
>> +++ b/include/linux/mem_encrypt.h
>> @@ -21,23 +21,11 @@
>>  
>>  #else	/* !CONFIG_ARCH_HAS_MEM_ENCRYPT */
>>  
>> -#define sme_me_mask	0ULL
>> -
>> -static inline bool sme_active(void) { return false; }
>>  static inline bool sev_active(void) { return false; }
>
> You want to move out sev_active as well, the only relevant thing is
> mem_encrypt_active(). Everything SME/SEV is an architecture detail.

I'm sure you saw it. I addressed sev_active in a separate patch.

Thanks for reviewing this series!

>> +static inline bool mem_encrypt_active(void) { return false; }
>
> Thanks,
>
> 	tglx


-- 
Thiago Jung Bauermann
IBM Linux Technology Center


WARNING: multiple messages have this Message-ID (diff)
From: Thiago Jung Bauermann <bauerman@linux.ibm.com>
To: Thomas Gleixner <tglx@linutronix.de>
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>, "H. Peter Anvin" <hpa@zytor.com>,
	linux-fsdevel@vger.kernel.org, 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: Thu, 18 Jul 2019 16:47:09 -0300	[thread overview]
Message-ID: <878ssv3z2a.fsf@morokweng.localdomain> (raw)
In-Reply-To: <alpine.DEB.2.21.1907121806160.1788@nanos.tec.linutronix.de>


Thomas Gleixner <tglx@linutronix.de> writes:

> On Fri, 12 Jul 2019, Thiago Jung Bauermann wrote:
>> diff --git a/include/linux/mem_encrypt.h b/include/linux/mem_encrypt.h
>> index b310a9c18113..f2e399fb626b 100644
>> --- a/include/linux/mem_encrypt.h
>> +++ b/include/linux/mem_encrypt.h
>> @@ -21,23 +21,11 @@
>>  
>>  #else	/* !CONFIG_ARCH_HAS_MEM_ENCRYPT */
>>  
>> -#define sme_me_mask	0ULL
>> -
>> -static inline bool sme_active(void) { return false; }
>>  static inline bool sev_active(void) { return false; }
>
> You want to move out sev_active as well, the only relevant thing is
> mem_encrypt_active(). Everything SME/SEV is an architecture detail.

I'm sure you saw it. I addressed sev_active in a separate patch.

Thanks for reviewing this series!

>> +static inline bool mem_encrypt_active(void) { return false; }
>
> Thanks,
>
> 	tglx


-- 
Thiago Jung Bauermann
IBM Linux Technology Center

_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu

  reply	other threads:[~2019-07-18 19:47 UTC|newest]

Thread overview: 79+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-12  5:36 [PATCH 0/3] Remove x86-specific code from generic headers Thiago Jung Bauermann
2019-07-12  5:36 ` Thiago Jung Bauermann
2019-07-12  5:36 ` Thiago Jung Bauermann
2019-07-12  5:36 ` [PATCH 1/3] x86/Kconfig: Move ARCH_HAS_MEM_ENCRYPT to arch/Kconfig Thiago Jung Bauermann
2019-07-12  5:36   ` Thiago Jung Bauermann
2019-07-12  5:36   ` Thiago Jung Bauermann
2019-07-12 16:04   ` Thomas Gleixner
2019-07-12 16:04     ` Thomas Gleixner
2019-07-12 16:04     ` Thomas Gleixner
2019-07-12 23:35     ` Thiago Jung Bauermann
2019-07-12 23:35       ` Thiago Jung Bauermann
2019-07-12 23:35       ` 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 [this message]
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
2019-07-12  5:36 ` [PATCH 3/3] fs/core/vmcore: Move sev_active() reference to x86 arch code Thiago Jung Bauermann
2019-07-12  5:36   ` Thiago Jung Bauermann
2019-07-12  5:36   ` Thiago Jung Bauermann
2019-07-12 13:09   ` Halil Pasic
2019-07-12 13:09     ` Halil Pasic
2019-07-12 13:09     ` Halil Pasic
2019-07-12 14:08     ` Christoph Hellwig
2019-07-12 14:08       ` Christoph Hellwig
2019-07-12 14:08       ` Christoph Hellwig
2019-07-12 14:51       ` Halil Pasic
2019-07-12 14:51         ` Halil Pasic
2019-07-12 14:51         ` Halil Pasic
2019-07-12 15:11         ` Christoph Hellwig
2019-07-12 15:11           ` Christoph Hellwig
2019-07-12 15:11           ` Christoph Hellwig
2019-07-12 15:42           ` Halil Pasic
2019-07-12 15:42             ` Halil Pasic
2019-07-12 15:42             ` Halil Pasic
2019-07-13  8:08             ` Christoph Hellwig
2019-07-13  8:08               ` Christoph Hellwig
2019-07-13  8:08               ` Christoph Hellwig
2019-07-12 21:55     ` Thiago Jung Bauermann
2019-07-12 21:55       ` Thiago Jung Bauermann
2019-07-12 21:55       ` Thiago Jung Bauermann
2019-07-12 21:55       ` Thiago Jung Bauermann
2019-07-15 14:03       ` Halil Pasic
2019-07-15 14:03         ` Halil Pasic
2019-07-15 14:03         ` Halil Pasic
2019-07-15 14:03         ` Halil Pasic
2019-07-15 14:30         ` Christoph Hellwig
2019-07-15 14:30           ` Christoph Hellwig
2019-07-15 14:30           ` Christoph Hellwig
2019-07-15 15:44           ` Lendacky, Thomas
2019-07-15 15:44             ` Lendacky, Thomas
2019-07-15 15:44             ` Lendacky, Thomas
2019-07-15 20:14           ` Thiago Jung Bauermann
2019-07-15 20:14             ` Thiago Jung Bauermann
2019-07-15 20:14             ` Thiago Jung Bauermann
2019-07-15 20:14             ` Thiago Jung Bauermann
2019-07-13  4:45 [PATCH 0/3] Remove x86-specific code from generic headers 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
2019-07-13  7:29     ` Christoph Hellwig
2019-07-13  7:29     ` Christoph Hellwig

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=878ssv3z2a.fsf@morokweng.localdomain \
    --to=bauerman@linux.ibm.com \
    --cc=adobriyan@gmail.com \
    --cc=andmike@linux.ibm.com \
    --cc=bp@alien8.de \
    --cc=hch@lst.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=m.szyprowski@samsung.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.