public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: Avi Kivity <avi@redhat.com>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"ddutile@redhat.com" <ddutile@redhat.com>,
	"mst@redhat.com" <mst@redhat.com>,
	"chrisw@redhat.com" <chrisw@redhat.com>
Subject: Re: [RFC PATCH 0/2] Expose available KVM free memory slot count to help avoid aborts
Date: Tue, 25 Jan 2011 12:13:51 -0700	[thread overview]
Message-ID: <1295982831.3230.90.camel@x201> (raw)
In-Reply-To: <4D3EFBDC.201@web.de>

On Tue, 2011-01-25 at 17:35 +0100, Jan Kiszka wrote:
> On 2011-01-25 15:53, Avi Kivity wrote:
> > On 01/25/2011 04:41 PM, Alex Williamson wrote:
> >> >  >
> >> >  >
> >> >  >  kvm: Allow memory slot array to grow on demand
> >> >  >
> >> >  >  Remove fixed KVM_MEMORY_SLOTS limit, allowing the slot array
> >> >  >  to grow on demand.  Private slots are now allocated at the
> >> >  >  front instead of the end.  Only x86 seems to use private slots,
> >> >
> >> >  Hmm, doesn't current user space expect slots 8..11 to be the private
> >> >  ones and wouldn't it cause troubles if slots 0..3 are suddenly
> >> reserved?
> >>
> >> The private slots aren't currently visible to userspace, they're
> >> actually slots 32..35.  The patch automatically increments user passed
> >> slot ids so userspace has it's own zero-based view of the array.
> >> Frankly, I don't understand why userspace reserves slots 8..11, is this
> >> compatibility with older kernel implementations?
> > 
> > I think so.  I believe these kernel versions are too old now to matter,
> > but of course I can't be sure.
> 
> Will check and enable those 4 additional slots for user space if we no
> longer need to exclude them.

Appears that the history goes something like this...

      * Once upon a time we had 8 memory slots

      * v2.6.24-4949-ge0d62c7 added 4 reserved slots above those 8

      * v2.6.24-4950-gcbc9402 made use of slot 8 for tss

      * v2.6.24-4962-gf78e0e2 made use of slot 9 for tpr

      * v2.6.25-5341-gef2979b bumped the 8 slots to 32

      * v2.6.26-rc1-13-gb7ebfb0 made use of slot 10 for ept

      * v2.6.28-4952-g6fe6397 moved the previously hard coded slots
        8,9,10 up to KVM_MEMORY_SLOTS + {0,1,2}

So we haven't needed to reserve 8..11 for a while and we've never made
use of all 4 private slots.  I should reduce that to 3 in my patch.
Maybe there's a test we could do in userspace to figure out we don't
have to skip those anymore?

Alex


  reply	other threads:[~2011-01-25 19:13 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-21 23:48 [RFC PATCH 0/2] Expose available KVM free memory slot count to help avoid aborts Alex Williamson
2011-01-21 23:48 ` [RFC PATCH 1/2] kvm: Allow querying free slots Alex Williamson
2011-01-21 23:48 ` [RFC PATCH 2/2] device-assignment: Count required kvm memory slots Alex Williamson
2011-01-22 22:11 ` [RFC PATCH 0/2] Expose available KVM free memory slot count to help avoid aborts Michael S. Tsirkin
2011-01-24  9:32 ` Marcelo Tosatti
2011-01-24 14:16   ` Jan Kiszka
2011-01-24 15:44     ` Alex Williamson
2011-01-25  5:37       ` Alex Williamson
2011-01-25  7:36         ` Jan Kiszka
2011-01-25 14:41           ` Alex Williamson
2011-01-25 14:45             ` Michael S. Tsirkin
2011-01-25 14:54               ` Avi Kivity
2011-01-25 14:53             ` Avi Kivity
2011-01-25 14:59               ` Michael S. Tsirkin
2011-01-25 17:33                 ` Avi Kivity
2011-01-25 17:58                   ` Michael S. Tsirkin
2011-01-26  9:17                     ` Avi Kivity
2011-01-26  9:20                       ` Michael S. Tsirkin
2011-01-26  9:23                         ` Avi Kivity
2011-01-26  9:39                           ` Michael S. Tsirkin
2011-01-26  9:54                             ` Avi Kivity
2011-01-26 12:08                               ` Michael S. Tsirkin
2011-01-27  9:21                                 ` Avi Kivity
2011-01-27  9:26                                   ` Michael S. Tsirkin
2011-01-27  9:28                                     ` Avi Kivity
2011-01-27  9:29                                       ` Michael S. Tsirkin
2011-01-27  9:51                                         ` Avi Kivity
2011-01-27  9:28                                     ` Michael S. Tsirkin
2011-01-25 16:35               ` Jan Kiszka
2011-01-25 19:13                 ` Alex Williamson [this message]
2011-01-26  8:14                   ` Jan Kiszka
2011-01-25 10:23         ` Avi Kivity
2011-01-25 14:57           ` Alex Williamson
2011-01-25 17:11             ` Avi Kivity
2011-01-25 17:43               ` Alex Williamson
2011-01-26  9:22                 ` Avi Kivity
2011-01-31 19:18         ` Marcelo Tosatti
2011-02-23 21:46           ` Alex Williamson
2011-02-24 12:34             ` Avi Kivity
2011-02-24 12:37               ` Avi Kivity
2011-02-24 18:10               ` Alex Williamson
2011-01-25 10:20   ` Avi Kivity
2011-01-25 14:46     ` Alex Williamson
2011-01-25 14:56       ` Avi Kivity
2011-01-25 14:55     ` Michael S. Tsirkin
2011-01-25 14:58       ` Avi Kivity
2011-01-25 15:23         ` Michael S. Tsirkin
2011-01-25 17:34           ` Avi Kivity
2011-01-25 18:00             ` Michael S. Tsirkin
2011-01-26  9:25               ` Avi Kivity

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=1295982831.3230.90.camel@x201 \
    --to=alex.williamson@redhat.com \
    --cc=avi@redhat.com \
    --cc=chrisw@redhat.com \
    --cc=ddutile@redhat.com \
    --cc=jan.kiszka@web.de \
    --cc=kvm@vger.kernel.org \
    --cc=mst@redhat.com \
    --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