qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
	Alexander Graf <agraf@suse.de>,
	qemu-devel@nongnu.org, Avi Kivity <avi@redhat.com>,
	anthony@codemonkey.ws, David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] [PATCH 6/6] kvm: Fix dirty tracking with large kernel page size
Date: Mon, 05 Mar 2012 08:17:28 +1100	[thread overview]
Message-ID: <1330895848.11728.81.camel@pasglop> (raw)
In-Reply-To: <4F539C4E.2090304@suse.de>

On Sun, 2012-03-04 at 17:46 +0100, Andreas Färber wrote:
> Except for ppcemb-softmmu (1k), which is irrelevant for KVM AFAIU.
> 
> Maybe just add an assert and be done with it?

Well, my patch should work anyway, as long as getpagesize() returns a
higher power of two.

The case that wouldn't work (but also doesn't exist) is getpagesize() <
TARGET_PAGE_SIZE.

> For the record, I am hoping to get rid of some of those cpu.h defines
> in a later stage of QOM'ification.

Cheers,
Ben.

  parent reply	other threads:[~2012-03-04 21:18 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-24  0:23 [Qemu-devel] [0/6] Assorted bugfixes David Gibson
2012-02-24  0:23 ` [Qemu-devel] [PATCH 1/6] kvm: Comparison with ioctl number macros needs to be unsigned David Gibson
2012-02-24  0:23 ` [Qemu-devel] [PATCH 2/6] slirp: Fix assertion failure on rejected DHCP requests David Gibson
2012-02-27 13:58   ` Jan Kiszka
2012-02-28  1:07     ` David Gibson
2012-02-24  0:23 ` [Qemu-devel] [PATCH 3/6] USB OHCI bug fixes David Gibson
2012-02-27 14:13   ` Gerd Hoffmann
2012-02-28  3:09     ` David Gibson
2012-02-28  3:37       ` David Gibson
2012-02-24  0:23 ` [Qemu-devel] [PATCH 4/6] Endian fixes for virtfs David Gibson
2012-02-24  8:29   ` Aneesh Kumar K.V
2012-02-24  0:23 ` [Qemu-devel] [PATCH 5/6] Endian fix an assertion in usb-msd David Gibson
2012-02-24  0:23 ` [Qemu-devel] [PATCH 6/6] kvm: Fix dirty tracking with large kernel page size David Gibson
2012-02-24  1:03   ` Benjamin Herrenschmidt
2012-02-26 21:41   ` Blue Swirl
2012-02-27  0:16     ` David Gibson
2012-02-27  0:25       ` Benjamin Herrenschmidt
2012-02-27  0:36     ` Alexander Graf
2012-03-03 15:29       ` Blue Swirl
2012-02-28 12:32   ` Avi Kivity
2012-02-28 21:48     ` Benjamin Herrenschmidt
2012-03-04 10:49       ` Avi Kivity
2012-03-04 11:53         ` Benjamin Herrenschmidt
2012-03-04 12:18           ` Avi Kivity
2012-03-04 16:46           ` Andreas Färber
2012-03-04 18:46             ` Alexander Graf
2012-03-04 20:21               ` Andreas Färber
2012-03-04 20:25                 ` Alexander Graf
2012-03-04 20:31                   ` Andreas Färber
2012-03-04 20:59                     ` Alexander Graf
2012-03-04 21:19                       ` Benjamin Herrenschmidt
2012-03-04 21:45                         ` Alexander Graf
2012-03-04 21:21                       ` Andreas Färber
2012-03-04 21:17             ` Benjamin Herrenschmidt [this message]
2012-02-28 23:32   ` Alexander Graf
2012-02-29  0:22     ` David Gibson

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=1330895848.11728.81.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=afaerber@suse.de \
    --cc=agraf@suse.de \
    --cc=anthony@codemonkey.ws \
    --cc=avi@redhat.com \
    --cc=david@gibson.dropbear.id.au \
    --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).