From: Jan Kiszka <jan.kiszka@web.de>
To: Avi Kivity <avi@redhat.com>
Cc: Takuya Yoshikawa <takuya.yoshikawa@gmail.com>,
mtosatti@redhat.com, kvm@vger.kernel.org,
yoshikawa.takuya@oss.ntt.co.jp, xiaoguangrong@cn.fujitsu.com,
Joerg.Roedel@amd.com
Subject: Re: [PATCH 1/1 v2] KVM: MMU: Optimize guest page table walk
Date: Tue, 26 Apr 2011 09:45:39 +0200 [thread overview]
Message-ID: <4DB67823.4010304@web.de> (raw)
In-Reply-To: <4DB6775F.9050207@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1710 bytes --]
On 2011-04-26 09:42, Avi Kivity wrote:
> On 04/25/2011 11:04 AM, Jan Kiszka wrote:
>> > +
>> > + ptep_user = (pt_element_t __user *)((void *)host_addr +
>> offset);
>> > + if (get_user(pte, ptep_user)) {
>> ^^^^^^^^^^^^
>> This doesn't work for x86-32: pte is 64 bit, but get_user is only
>> defined up to 32 bit on that platform.
>>
>
> I actually considered this, and saw:
>
> #ifdef CONFIG_X86_32
> #define __get_user_8(__ret_gu, __val_gu, ptr) \
> __get_user_x(X, __ret_gu, __val_gu, ptr)
> #else
> #define __get_user_8(__ret_gu, __val_gu, ptr) \
> __get_user_x(8, __ret_gu, __val_gu, ptr)
> #endif
>
> #define get_user(x, ptr) \
> ({ \
> int __ret_gu; \
> unsigned long __val_gu; \
> __chk_user_ptr(ptr); \
> might_fault(); \
> switch (sizeof(*(ptr))) { \
>
> ...
>
> case 8: \
> __get_user_8(__ret_gu, __val_gu, ptr); \
> break; \
>
> ...
>
> } \
> (x) = (__typeof__(*(ptr)))__val_gu; \
> __ret_gu; \
> })
>
> so it should work. How does it fail?
On x86-32, the above macro resolves to __get_user_X, an undefined symbol.
>
>> Avi, what's your 32-bit buildbot doing? :)
>
> I regularly autotest on x86_64, not on i386, sorry.
Good that it's included in my kvm-kmod buildbot.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]
next prev parent reply other threads:[~2011-04-26 7:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-21 15:32 [PATCH 0/1 v2] KVM: MMU: Optimize guest page table walk Takuya Yoshikawa
2011-04-21 15:34 ` [PATCH 1/1 " Takuya Yoshikawa
2011-04-24 7:27 ` Avi Kivity
2011-04-24 13:15 ` Takuya Yoshikawa
2011-04-25 8:04 ` Jan Kiszka
2011-04-25 8:32 ` Takuya Yoshikawa
2011-04-25 9:15 ` Jan Kiszka
2011-04-26 4:50 ` Takuya Yoshikawa
2011-04-26 6:34 ` Jan Kiszka
2011-04-26 14:40 ` Takuya Yoshikawa
2011-04-26 14:54 ` Avi Kivity
2011-04-26 15:13 ` Takuya Yoshikawa
2011-04-26 17:15 ` Avi Kivity
2011-04-26 16:26 ` Takuya Yoshikawa
2011-04-26 17:16 ` Avi Kivity
2011-04-26 7:42 ` Avi Kivity
2011-04-26 7:45 ` Jan Kiszka [this message]
2011-04-26 8:21 ` Avi Kivity
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=4DB67823.4010304@web.de \
--to=jan.kiszka@web.de \
--cc=Joerg.Roedel@amd.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=takuya.yoshikawa@gmail.com \
--cc=xiaoguangrong@cn.fujitsu.com \
--cc=yoshikawa.takuya@oss.ntt.co.jp \
/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).