qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Michael S. Tsirkin" <mst@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, 04 Nov 2013 13:11:36 +0100	[thread overview]
Message-ID: <52778EF8.4090006@redhat.com> (raw)
In-Reply-To: <20131104120431.GA26395@redhat.com>

Il 04/11/2013 13:04, Michael S. Tsirkin ha scritto:
> > > > 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.
> 
> Hmm I think it's *at most* that deep but can be more shallow, no?

Yes, but it gets more shallow only if you have very large regions (which
is obviously not the case for io space).  The levels always cover the
same bit range (e.g. bits 42-51 for the first level on x86).

Paolo

  reply	other threads:[~2013-11-04 12:12 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
2013-11-04 12:11             ` Paolo Bonzini [this message]
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=52778EF8.4090006@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=afaerber@suse.de \
    --cc=jan.kiszka@siemens.com \
    --cc=marcel.a@redhat.com \
    --cc=mst@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 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).