From: Avi Kivity <avi@redhat.com>
To: Eric Northup <digitaleric@google.com>
Cc: kvm@vger.kernel.org, Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: [PATCH RFC] KVM MMU: fix hashing for TDP and non-paging modes
Date: Mon, 26 Apr 2010 12:24:50 +0300 [thread overview]
Message-ID: <4BD55BE2.1030500@redhat.com> (raw)
In-Reply-To: <4BD18046.8020905@redhat.com>
On 04/23/2010 02:11 PM, Avi Kivity wrote:
>
>> All feedback would be welcome, since I'm new to this system! A
>> strawman patch follows.
>>
>
> Patch is correct, but I have already fixed this in a more extensive
> patch set (that also folds the 32-bit and 64-bit cases together, etc.)
> and I'm too lazy to rebase on top of yours.
Well my patchset is broken. Marcelo, please apply this and I'll rebase
and fix.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-04-26 9:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-22 21:15 [PATCH RFC] KVM MMU: fix hashing for TDP and non-paging modes Eric Northup
2010-04-23 11:11 ` Avi Kivity
2010-04-26 9:24 ` Avi Kivity [this message]
2010-04-26 21:30 ` Marcelo Tosatti
2010-04-26 21:46 ` Marcelo Tosatti
2010-04-27 0:00 ` Eric Northup
2010-04-27 12:31 ` Marcelo Tosatti
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=4BD55BE2.1030500@redhat.com \
--to=avi@redhat.com \
--cc=digitaleric@google.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.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