public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Claudio Imbrenda <imbrenda@linux.ibm.com>
To: Nico Boehr <nrb@linux.ibm.com>
Cc: borntraeger@linux.ibm.com, frankja@linux.ibm.com,
	kvm@vger.kernel.org, linux-s390@vger.kernel.org,
	pasic@linux.ibm.com, akrowiak@linux.ibm.com,
	jjherne@linux.ibm.com, mimu@linux.ibm.com, vneethv@linux.ibm.com,
	oberpar@linux.ibm.com
Subject: Re: [PATCH v1] KVM: s390: GISA: sort out physical vs virtual pointers usage
Date: Tue, 8 Nov 2022 13:50:38 +0100	[thread overview]
Message-ID: <20221108135038.4b6300e4@p-imbrenda> (raw)
In-Reply-To: <20221107085727.1533792-1-nrb@linux.ibm.com>

On Mon,  7 Nov 2022 09:57:27 +0100
Nico Boehr <nrb@linux.ibm.com> wrote:

> Fix virtual vs physical address confusion (which currently are the same).
> 
> In chsc_sgib(), do the virtual-physical conversion in the caller since
> the caller needs to make sure it is a 31-bit address and zero has a
> special meaning (disassociating the GIB).
> 
> Signed-off-by: Nico Boehr <nrb@linux.ibm.com>

Reviewed-by: Claudio Imbrenda <imbrenda@linux.ibm.com>

> ---
>  arch/s390/kvm/interrupt.c | 11 +++++++----
>  1 file changed, 7 insertions(+), 4 deletions(-)
> 
> diff --git a/arch/s390/kvm/interrupt.c b/arch/s390/kvm/interrupt.c
> index ab569faf0df2..ae018217eac8 100644
> --- a/arch/s390/kvm/interrupt.c
> +++ b/arch/s390/kvm/interrupt.c
> @@ -3104,9 +3104,9 @@ static enum hrtimer_restart gisa_vcpu_kicker(struct hrtimer *timer)
>  static void process_gib_alert_list(void)
>  {
>  	struct kvm_s390_gisa_interrupt *gi;
> +	u32 final, gisa_phys, origin = 0UL;
>  	struct kvm_s390_gisa *gisa;
>  	struct kvm *kvm;
> -	u32 final, origin = 0UL;
>  
>  	do {
>  		/*
> @@ -3132,9 +3132,10 @@ static void process_gib_alert_list(void)
>  		 * interruptions asap.
>  		 */
>  		while (origin & GISA_ADDR_MASK) {
> -			gisa = (struct kvm_s390_gisa *)(u64)origin;
> +			gisa_phys = origin;
> +			gisa = phys_to_virt(gisa_phys);
>  			origin = gisa->next_alert;
> -			gisa->next_alert = (u32)(u64)gisa;
> +			gisa->next_alert = gisa_phys;
>  			kvm = container_of(gisa, struct sie_page2, gisa)->kvm;
>  			gi = &kvm->arch.gisa_int;
>  			if (hrtimer_active(&gi->timer))
> @@ -3418,6 +3419,7 @@ void kvm_s390_gib_destroy(void)
>  
>  int kvm_s390_gib_init(u8 nisc)
>  {
> +	u32 gib_origin;
>  	int rc = 0;
>  
>  	if (!css_general_characteristics.aiv) {
> @@ -3439,7 +3441,8 @@ int kvm_s390_gib_init(u8 nisc)
>  	}
>  
>  	gib->nisc = nisc;
> -	if (chsc_sgib((u32)(u64)gib)) {
> +	gib_origin = virt_to_phys(gib);
> +	if (chsc_sgib(gib_origin)) {
>  		pr_err("Associating the GIB with the AIV facility failed\n");
>  		free_page((unsigned long)gib);
>  		gib = NULL;


  reply	other threads:[~2022-11-08 12:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-07  8:57 [PATCH v1] KVM: s390: GISA: sort out physical vs virtual pointers usage Nico Boehr
2022-11-08 12:50 ` Claudio Imbrenda [this message]
2022-11-24 11:48 ` Michael Mueller

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=20221108135038.4b6300e4@p-imbrenda \
    --to=imbrenda@linux.ibm.com \
    --cc=akrowiak@linux.ibm.com \
    --cc=borntraeger@linux.ibm.com \
    --cc=frankja@linux.ibm.com \
    --cc=jjherne@linux.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=mimu@linux.ibm.com \
    --cc=nrb@linux.ibm.com \
    --cc=oberpar@linux.ibm.com \
    --cc=pasic@linux.ibm.com \
    --cc=vneethv@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