public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: David Hildenbrand <david@redhat.com>
Cc: KVM <kvm@vger.kernel.org>,
	linux-s390@vger.kernel.org,
	Christian Borntraeger <borntraeger@de.ibm.com>
Subject: Re: [PATCH v2] KVM: s390: cleanup struct kvm_s390_float_interrupt
Date: Tue, 9 Jan 2018 14:55:14 +0100	[thread overview]
Message-ID: <20180109145514.619eb7c3.cohuck@redhat.com> (raw)
In-Reply-To: <20180108193747.10818-1-david@redhat.com>

On Mon,  8 Jan 2018 20:37:47 +0100
David Hildenbrand <david@redhat.com> wrote:

> "wq" is not used at all.

That seems to date back to 66933b78e3204057bfc26343afcd0d463c0e8e55.

> "cpuflags" can be access directly via the vcpu,
> just as "float_int" via vcpu->kvm.

I'm trying to remember whether there were any caching/locality issues,
but I don't think so.

> 
> Signed-off-by: David Hildenbrand <david@redhat.com>
> ---
> 
> v1 -> v2:
> - Properly make use of dst_vcpu instead of vcpu in sigp.c
> 
>  arch/s390/include/asm/kvm_host.h |  3 ---
>  arch/s390/kvm/interrupt.c        | 25 +++++++++++--------------
>  arch/s390/kvm/kvm-s390.c         |  3 ---
>  arch/s390/kvm/kvm-s390.h         |  2 +-
>  arch/s390/kvm/sigp.c             | 12 ++++--------
>  5 files changed, 16 insertions(+), 29 deletions(-)
> 

> diff --git a/arch/s390/kvm/interrupt.c b/arch/s390/kvm/interrupt.c
> index 818aa4248b0f..f8eb2cfa763a 100644
> --- a/arch/s390/kvm/interrupt.c
> +++ b/arch/s390/kvm/interrupt.c
> @@ -107,12 +107,11 @@ static int sca_inject_ext_call(struct kvm_vcpu *vcpu, int src_id)
>  
>  static void sca_clear_ext_call(struct kvm_vcpu *vcpu)
>  {
> -	struct kvm_s390_local_interrupt *li = &vcpu->arch.local_int;
>  	int rc, expect;
>  
>  	if (!kvm_s390_use_sca_entries())
>  		return;
> -	atomic_andnot(CPUSTAT_ECALL_PEND, li->cpuflags);
> +	atomic_andnot(CPUSTAT_ECALL_PEND, &vcpu->arch.sie_block->cpuflags);

We have __set_cpuflag() to set a flag; do we also want
__clear_cpuflag()? Would make the code nicer, I think. (There are more
possible callers for that.)

>  	read_lock(&vcpu->kvm->arch.sca_lock);
>  	if (vcpu->kvm->arch.use_esca) {
>  		struct esca_block *sca = vcpu->kvm->arch.sca;

  reply	other threads:[~2018-01-09 13:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-08 19:37 [PATCH v2] KVM: s390: cleanup struct kvm_s390_float_interrupt David Hildenbrand
2018-01-09 13:55 ` Cornelia Huck [this message]
2018-01-10 11:39   ` David Hildenbrand
2018-01-10 11:51     ` Christian Borntraeger
2018-01-10 11:30 ` Christian Borntraeger
2018-01-10 11:56   ` David Hildenbrand
2018-01-10 12:20     ` Cornelia Huck
2018-01-10 13:09 ` Christian Borntraeger

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=20180109145514.619eb7c3.cohuck@redhat.com \
    --to=cohuck@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=david@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-s390@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox