From: Cornelia Huck <cornelia.huck@de.ibm.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Gleb Natapov <gleb@kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>,
kvm@vger.kernel.org, Thomas Huth <thuth@linux.vnet.ibm.com>,
Dominik Dingel <dingel@linux.vnet.ibm.com>
Subject: Re: [PULL 1/1] KVM: s390: Fix memory access error detection
Date: Mon, 20 Jan 2014 13:00:02 +0100 [thread overview]
Message-ID: <20140120130002.29d01053@gondolin> (raw)
In-Reply-To: <1390218843-15196-2-git-send-email-borntraeger@de.ibm.com>
On Mon, 20 Jan 2014 12:54:03 +0100
Christian Borntraeger <borntraeger@de.ibm.com> wrote:
> Seems that commit 210b1607012cc9034841a393e0591b2c86d9e26c
> (KVM: s390: Removed SIE_INTERCEPT_UCONTROL) lost a hunk when we
> reworked our patch queue to rework the async_fp code. We now
> ignore faults on the sie instruction (guest accesses non-existing
> memory) instead of sending a fault into the guest. This leads to
> hang situations with the old virtio transport that checks for
> descriptor memory after guest memory. Instead of bailing out this
> code now goes wild...
> Lets re-add the check.
>
> Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
Acked-by: Cornelia Huck <cornelia.huck@de.ibm.com>
> ---
> arch/s390/kvm/kvm-s390.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/arch/s390/kvm/kvm-s390.c b/arch/s390/kvm/kvm-s390.c
> index 1bb1dda..7635c00 100644
> --- a/arch/s390/kvm/kvm-s390.c
> +++ b/arch/s390/kvm/kvm-s390.c
> @@ -738,6 +738,10 @@ static int vcpu_post_run(struct kvm_vcpu *vcpu, int exit_reason)
> current->thread.gmap_addr;
> vcpu->run->s390_ucontrol.pgm_code = 0x10;
> rc = -EREMOTE;
> + } else {
> + VCPU_EVENT(vcpu, 3, "%s", "fault in sie instruction");
> + trace_kvm_s390_sie_fault(vcpu);
> + rc = kvm_s390_inject_program_int(vcpu, PGM_ADDRESSING);
> }
>
> memcpy(&vcpu->run->s.regs.gprs[14], &vcpu->arch.sie_block->gg14, 16);
next prev parent reply other threads:[~2014-01-20 12:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-20 11:54 [PULL 0/1] KVM: s390: urgent fix for kvm/next Christian Borntraeger
2014-01-20 11:54 ` [PULL 1/1] KVM: s390: Fix memory access error detection Christian Borntraeger
2014-01-20 12:00 ` Cornelia Huck [this message]
2014-01-20 11:58 ` [PULL 0/1] KVM: s390: urgent fix for kvm/next Paolo Bonzini
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=20140120130002.29d01053@gondolin \
--to=cornelia.huck@de.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=dingel@linux.vnet.ibm.com \
--cc=gleb@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=thuth@linux.vnet.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 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.