All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
	"Marcel Apfelbaum" <marcel.a@redhat.com>,
	"Jan Kiszka" <jan.kiszka@siemens.com>,
	qemu-devel@nongnu.org, "Andreas Färber" <afaerber@suse.de>,
	"Richard Henderson" <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH] exec: limit system memory size
Date: Mon, 4 Nov 2013 14:04:31 +0200	[thread overview]
Message-ID: <20131104120431.GA26395@redhat.com> (raw)
In-Reply-To: <5277837B.10105@redhat.com>

On Mon, Nov 04, 2013 at 12:22:35PM +0100, Paolo Bonzini wrote:
> Il 04/11/2013 12:14, Michael S. Tsirkin ha scritto:
> >> > 
> >> > This patch looks good; however, on top of it can you test 
> >> > kvm-unit-tests with TARGET_PHYS_ADDR_SPACE_BITS=64 and see whether 
> >> > there is a measurable slowdown (in the inl_from_qemu tests)?  If not, 
> >> > we can just get rid of TARGET_PHYS_ADDR_SPACE_BITS in exec.c.
> > I'd rather we fixed a bug first - we need to fix it on stable too - any
> > cleanups can come on top.
> 
> This is not necessarily a cleanup.  Getting rid of
> TARGET_PHYS_ADDR_SPACE_BITS in exec.c means fixing device-to-device DMA
> bugs for example.
> 
> Of course a smaller patch can be done that avoids the renaming of L2_*
> constants.
> 
> > Also, I'm not sure what will this test tell
> > us: inl reads io space, not memory, right?
> 
> The number of levels in the dispatch radix tree is independent of the
> size of the AddressSpace; it is P_L2_LEVELS for both the 64K io space
> and the 2^TARGET_PHYS_ADDRESS_SPACE_BITS memory space.
> 
> Paolo

Hmm I think it's *at most* that deep but can be more shallow, no?

-- 
MST

  reply	other threads:[~2013-11-04 12:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-04  6:06 [Qemu-devel] [PATCH] exec: limit system memory size Michael S. Tsirkin
2013-11-04  6:15 ` Michael S. Tsirkin
2013-11-04  9:50 ` Marcel Apfelbaum
2013-11-04 10:07   ` Michael S. Tsirkin
2013-11-04 10:54     ` Paolo Bonzini
2013-11-04 11:14       ` Michael S. Tsirkin
2013-11-04 11:22         ` Paolo Bonzini
2013-11-04 12:04           ` Michael S. Tsirkin [this message]
2013-11-04 12:11             ` Paolo Bonzini
2013-11-04 12:26 ` Paolo Bonzini

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=20131104120431.GA26395@redhat.com \
    --to=mst@redhat.com \
    --cc=afaerber@suse.de \
    --cc=jan.kiszka@siemens.com \
    --cc=marcel.a@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.