From: Alexander Graf <agraf@suse.de>
To: Mihai Caraman <mihai.caraman@freescale.com>, kvm-ppc@vger.kernel.org
Cc: linuxppc-dev@lists.ozlabs.org, kvm@vger.kernel.org
Subject: Re: [PATCH v6 0/5] Read guest last instruction from kvmppc_get_last_inst()
Date: Thu, 24 Jul 2014 15:08:07 +0200 [thread overview]
Message-ID: <53D10537.8030906@suse.de> (raw)
In-Reply-To: <1406131582-6052-1-git-send-email-mihai.caraman@freescale.com>
On 23.07.14 18:06, Mihai Caraman wrote:
> Read guest last instruction from kvmppc_get_last_inst() allowing the function
> to fail in order to emulate again. On bookehv architecture search for
> the physical address and kmap it, instead of using Load External PID (lwepx)
> instruction. This fixes an infinite loop caused by lwepx's data TLB miss
> exception handled in the host and the TODO for execute-but-not-read entries
> and TLB eviction.
>
> Mihai Caraman (5):
> KVM: PPC: e500mc: Revert "add load inst fixup"
> KVM: PPC: Book3e: Add TLBSEL/TSIZE defines for MAS0/1
> KVM: PPC: Book3s: Remove kvmppc_read_inst() function
> KVM: PPC: Alow kvmppc_get_last_inst() to fail
> KVM: PPC: Bookehv: Get vcpu's last instruction for emulation
Thanks, applied to kvm-ppc-queue.
Alex
prev parent reply other threads:[~2014-07-24 13:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-23 16:06 [PATCH v6 0/5] Read guest last instruction from kvmppc_get_last_inst() Mihai Caraman
2014-07-23 16:06 ` [PATCH v6 1/5] KVM: PPC: e500mc: Revert "add load inst fixup" Mihai Caraman
2014-07-23 16:06 ` [PATCH v6 2/5] KVM: PPC: Book3e: Add TLBSEL/TSIZE defines for MAS0/1 Mihai Caraman
2014-07-23 16:06 ` [PATCH v6 3/5] KVM: PPC: Book3s: Remove kvmppc_read_inst() function Mihai Caraman
2014-07-23 16:06 ` [PATCH v6 4/5] KVM: PPC: Alow kvmppc_get_last_inst() to fail Mihai Caraman
2014-07-23 16:06 ` [PATCH v6 5/5] KVM: PPC: Bookehv: Get vcpu's last instruction for emulation Mihai Caraman
2014-07-24 13:08 ` Alexander Graf [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=53D10537.8030906@suse.de \
--to=agraf@suse.de \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mihai.caraman@freescale.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;
as well as URLs for NNTP newsgroup(s).