From: Jes Sorensen <jes@sgi.com>
To: kvm-ia64@vger.kernel.org
Subject: Re: [patch] fix kvm_arch_vcpu_ioctl_[gs]et_regs() - v2
Date: Thu, 18 Dec 2008 10:26:50 +0000 [thread overview]
Message-ID: <494A256A.4000908@sgi.com> (raw)
In-Reply-To: <4947CD2B.5030300@sgi.com>
Avi Kivity wrote:
> Jes Sorensen wrote:
>>
>> Please don't do that, then they'll end up after a 16KB struct, I put
>> them where they were deliberately.
> Why does it matter? I don't see any performance issue, we copy
> everything anyway, and this is not a high usage interface.
Well it just makes the generated code uglier.
Jes
next prev parent reply other threads:[~2008-12-18 10:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-16 15:45 [patch] fix kvm_arch_vcpu_ioctl_[gs]et_regs() - v2 Jes Sorensen
2008-12-17 1:41 ` Zhang, Xiantao
2008-12-17 1:41 ` Zhang, Xiantao
2008-12-17 10:32 ` Avi Kivity
2008-12-17 10:32 ` Avi Kivity
2008-12-18 9:13 ` Jes Sorensen
2008-12-18 10:11 ` Avi Kivity
2008-12-18 10:26 ` Jes Sorensen [this message]
2008-12-18 11:19 ` Avi Kivity
2008-12-18 11:21 ` 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=494A256A.4000908@sgi.com \
--to=jes@sgi.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