qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: aliguori@us.ibm.com, mtosatti@redhat.com, jan.kiszka@web.de,
	qemu-devel@nongnu.org, David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] [PATCH, RESEND] kvm: Fix dirty tracking with large kernel page size
Date: Thu, 10 May 2012 12:27:09 +0300	[thread overview]
Message-ID: <4FAB89ED.2040500@redhat.com> (raw)
In-Reply-To: <4FAAEE6D.3030608@codemonkey.ws>

On 05/10/2012 01:23 AM, Anthony Liguori wrote:
> On 04/04/2012 03:41 AM, Avi Kivity wrote:
>> On 04/04/2012 04:15 AM, David Gibson wrote:
>>> If the kernel page size is larger than TARGET_PAGE_SIZE, which
>>> happens for example on ppc64 with kernels compiled for 64K pages,
>>> the dirty tracking doesn't work.
>>>
>>> Cc: Avi Kivity<avi@redhat.com>
>>> Cc: Marcelo Tosatti<mtosatti@redhat.com>
>>>
>>
>> Thanks, applied to uq/master.
>
> Can ya'll send a PULL request for 1.1 with any bug fixes from uq/master?

Sure, I'll trawl the list for missed patches (Jan, any known?) and let
autotest at it.

-- 
error compiling committee.c: too many arguments to function

  reply	other threads:[~2012-05-10  9:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-04  1:15 [Qemu-devel] [PATCH, RESEND] kvm: Fix dirty tracking with large kernel page size David Gibson
2012-04-04  8:41 ` Avi Kivity
2012-05-09 22:23   ` Anthony Liguori
2012-05-10  9:27     ` Avi Kivity [this message]
2012-05-10 10:49       ` Jan Kiszka
2012-05-10 10:55         ` Avi Kivity
  -- strict thread matches above, loose matches on Subject: below --
2012-04-02  4:04 David Gibson
2012-04-02  4:14 ` Benjamin Herrenschmidt
2012-04-03  7:08 ` Jan Kiszka
2012-04-04  1:12   ` David Gibson
2012-04-04 10:58     ` Jan Kiszka
2012-04-04 14:24       ` David Gibson
2012-04-05  7:32         ` Jan Kiszka

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=4FAB89ED.2040500@redhat.com \
    --to=avi@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=anthony@codemonkey.ws \
    --cc=david@gibson.dropbear.id.au \
    --cc=jan.kiszka@web.de \
    --cc=mtosatti@redhat.com \
    --cc=qemu-devel@nongnu.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 NNTP newsgroup(s).