public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Borntraeger <borntraeger@linux.ibm.com>
To: Nico Boehr <nrb@linux.ibm.com>,
	frankja@linux.ibm.com, imbrenda@linux.ibm.com
Cc: kvm@vger.kernel.org, linux-s390@vger.kernel.org
Subject: Re: [PATCH v1] s390/mm: fix virtual-physical address confusion for swiotlb
Date: Mon, 7 Nov 2022 12:21:58 +0100	[thread overview]
Message-ID: <86aa57d3-e92e-4846-8676-cb2f93dcf59c@linux.ibm.com> (raw)
In-Reply-To: <20221107105843.6641-1-nrb@linux.ibm.com>

Am 07.11.22 um 11:58 schrieb Nico Boehr:
> swiotlb passes virtual addresses to set_memory_encrypted() and
> set_memory_decrypted(), but uv_remove_shared() and uv_set_shared()
> expect physical addresses. This currently works, because virtual
> and physical addresses are the same.
> 
> Add virt_to_phys() to resolve the virtual-physical confusion.
> 
> Reported-by: Marc Hartmayer <mhartmay@linux.ibm.com>
> Signed-off-by: Nico Boehr <nrb@linux.ibm.com>

Reviewed-by: Christian Borntraeger <borntraeger@linux.ibm.com>

I am asking myself if we should rename addr to vaddr to make this more obvious.
(Other users of these functions do use vaddr as well).

> ---
>   arch/s390/mm/init.c | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/arch/s390/mm/init.c b/arch/s390/mm/init.c
> index 97d66a3e60fb..8b652654064e 100644
> --- a/arch/s390/mm/init.c
> +++ b/arch/s390/mm/init.c
> @@ -146,7 +146,7 @@ int set_memory_encrypted(unsigned long addr, int numpages)
>   
>   	/* make specified pages unshared, (swiotlb, dma_free) */
>   	for (i = 0; i < numpages; ++i) {
> -		uv_remove_shared(addr);
> +		uv_remove_shared(virt_to_phys((void *)addr));
>   		addr += PAGE_SIZE;
>   	}
>   	return 0;
> @@ -157,7 +157,7 @@ int set_memory_decrypted(unsigned long addr, int numpages)
>   	int i;
>   	/* make specified pages shared (swiotlb, dma_alloca) */
>   	for (i = 0; i < numpages; ++i) {
> -		uv_set_shared(addr);
> +		uv_set_shared(virt_to_phys((void *)addr));
>   		addr += PAGE_SIZE;
>   	}
>   	return 0;

  reply	other threads:[~2022-11-07 11:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-07 10:58 [PATCH v1] s390/mm: fix virtual-physical address confusion for swiotlb Nico Boehr
2022-11-07 11:21 ` Christian Borntraeger [this message]
2022-11-07 12:06   ` Nico Boehr

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=86aa57d3-e92e-4846-8676-cb2f93dcf59c@linux.ibm.com \
    --to=borntraeger@linux.ibm.com \
    --cc=frankja@linux.ibm.com \
    --cc=imbrenda@linux.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=nrb@linux.ibm.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox