From: Avi Kivity <avi@redhat.com>
To: kvm-ia64@vger.kernel.org
Subject: Re: [PATCH RFC v2 3/6] KVM: introduce a wrapper function to copy
Date: Fri, 23 Apr 2010 10:26:06 +0000 [thread overview]
Message-ID: <4BD175BE.7040307@redhat.com> (raw)
In-Reply-To: <20100420195913.ac44281c.yoshikawa.takuya@oss.ntt.co.jp>
On 04/22/2010 11:57 AM, Takuya Yoshikawa wrote:
>
> And about x86_32 copy_in_user().
>
> They are using copy_user_generic() which is implemented only for 64bit.
>
> So I'll show them current copy_from_user() and copy_to_user() version and
> see their response.
>
> If rejected, though I hope not, please give me another option, OK?
>
If we can justify it, I doubt it will be rejected, but in case it does,
we'll work something out.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
prev parent reply other threads:[~2010-04-23 10:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-20 10:59 [PATCH RFC v2 3/6] KVM: introduce a wrapper function to copy dirty Takuya Yoshikawa
2010-04-21 11:12 ` [PATCH RFC v2 3/6] KVM: introduce a wrapper function to copy Avi Kivity
2010-04-22 8:57 ` Takuya Yoshikawa
2010-04-23 10:26 ` Avi Kivity [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=4BD175BE.7040307@redhat.com \
--to=avi@redhat.com \
--cc=kvm-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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).