From: Jes Sorensen <jes@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [patch] fix zero extending for mmio ld1/2/4 emulation in KVM
Date: Thu, 22 May 2008 08:08:59 +0000 [thread overview]
Message-ID: <48352A1B.5080907@sgi.com> (raw)
In-Reply-To: <4832A0A6.8050800@sgi.com>
Isaku Yamahata wrote:
> Hi Jes.
>
> Good catch.
> I thought similar fix is necessary for xen/ia64 and checked the code.
> It was fixed differently. I think the unnecessary divergence is undesirable.
> What do you think the following fix according?
Hi Isaku,
I tried this fix for KVM, but it didn't work since the data returned is
a full word (64 bit) and it seems to get crippled in the process, so
we cannot use your patch :(
Cheers,
Jes
>
> Only copy in the data actually requested by the instruction emulation
> and zero pad the destination register first. This avoids the problem
> where emulated mmio access got garbled data from ld2.acq instructions
> in the vga console driver.
>
> Signed-off-by: Isaku Yamahata <yamahata@valinux.co.jp>
> Cc: Jes Sorensen <jes@sgi.com>
>
> diff --git a/arch/ia64/kvm/mmio.c b/arch/ia64/kvm/mmio.c
> index 351bf70..e6f194a 100644
> --- a/arch/ia64/kvm/mmio.c
> +++ b/arch/ia64/kvm/mmio.c
> @@ -154,6 +154,9 @@ static void mmio_access(struct kvm_vcpu *vcpu, u64 src_pa, u64 *dest,
> p->u.ioreq.dir = dir;
> if (dir = IOREQ_WRITE)
> p->u.ioreq.data = *dest;
> + else
> + /* it's necessary to ensure zero extending */
> + p->u.ioreq.data = 0;
> p->u.ioreq.state = STATE_IOREQ_READY;
> vmm_transition(vcpu);
>
>
>
> On Tue, May 20, 2008 at 01:13:50PM +0200, Jes Sorensen wrote:
>> Matthew Chapman wrote:
>>> Jes,
>>>
>>> Glad you tracked it down. Can I suggest rather than using memcpy, a
>>> more efficient way might be something like...
>>>
>>> #define ZERO_EXTEND(x,bits) ((x) & (~0UL >> (64-(bits))))
>>>
>>> *dest = ZERO_EXTEND(p->u.ioreq.data, 8*s);
>> Much nicer indeed!
>>
>> Here's a pretty version - Tony will you apply this one instead.
>>
>> Cheers,
>> Jes
>>
>>
>
>> Only copy in the data actually requested by the instruction emulation
>> and zero pad the destination register first. This avoids the problem
>> where emulated mmio access got garbled data from ld2.acq instructions
>> in the vga console driver.
>>
>> Signed-off-by: Jes Sorensen <jes@sgi.com>
>>
>> ---
>> arch/ia64/kvm/mmio.c | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> Index: linux-2.6.git/arch/ia64/kvm/mmio.c
>> =================================>> --- linux-2.6.git.orig/arch/ia64/kvm/mmio.c
>> +++ linux-2.6.git/arch/ia64/kvm/mmio.c
>> @@ -159,7 +159,8 @@
>>
>> if (p->u.ioreq.state = STATE_IORESP_READY) {
>> if (dir = IOREQ_READ)
>> - *dest = p->u.ioreq.data;
>> + /* it's necessary to ensure zero extending */
>> + *dest = p->u.ioreq.data & (~0UL >> (64-(s*8)));
>> } else
>> panic_vm(vcpu);
>> out:
>
>
next prev parent reply other threads:[~2008-05-22 8:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-20 9:57 [patch] fix zero extending for mmio ld1/2/4 emulation in KVM Jes Sorensen
2008-05-20 10:33 ` Matthew Chapman
2008-05-20 11:13 ` Jes Sorensen
2008-05-21 9:46 ` Zhang, Xiantao
2008-05-21 10:05 ` Avi Kivity
2008-05-22 3:45 ` Isaku Yamahata
2008-05-22 8:08 ` Jes Sorensen [this message]
2008-05-22 15:16 ` Xu, Anthony
2008-05-22 15:23 ` Jes Sorensen
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=48352A1B.5080907@sgi.com \
--to=jes@sgi.com \
--cc=linux-ia64@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