From: David Hildenbrand <david@redhat.com>
To: KVM <kvm@vger.kernel.org>
Cc: linux-s390@vger.kernel.org,
Christian Borntraeger <borntraeger@de.ibm.com>,
Cornelia Huck <cohuck@redhat.com>
Subject: Re: [PATCH v1] KVM: s390: cleanup struct kvm_s390_float_interrupt
Date: Mon, 8 Jan 2018 14:42:23 +0100 [thread overview]
Message-ID: <67f05b75-f5fe-7da3-ea37-df9743a4a278@redhat.com> (raw)
In-Reply-To: <20180108134013.32285-1-david@redhat.com>
> u64 *reg)
> {
> - struct kvm_s390_local_interrupt *li;
> int cpuflags;
> int rc;
> int ext_call_pending;
>
> - li = &dst_vcpu->arch.local_int;
> -
> - cpuflags = atomic_read(li->cpuflags);
> + cpuflags = atomic_read(&vcpu->arch.sie_block->cpuflags);
Wonder why I always see errors just after sending the patch :)
vcpu -> dst_vcpu
--
Thanks,
David / dhildenb
prev parent reply other threads:[~2018-01-08 13:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-08 13:40 [PATCH v1] KVM: s390: cleanup struct kvm_s390_float_interrupt David Hildenbrand
2018-01-08 13:42 ` David Hildenbrand [this message]
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=67f05b75-f5fe-7da3-ea37-df9743a4a278@redhat.com \
--to=david@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@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