public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Avi Kivity <avi@qumranet.com>
Cc: kvm <kvm@vger.kernel.org>, Carsten Otte <cotte@de.ibm.com>,
	Olaf Schnapper <os@de.ibm.com>,
	Christian Ehrhardt <ehrhardt@linux.vnet.ibm.com>,
	Izik Eidus <izike@qumranet.com>
Subject: Re: [PATCH] kvm-userspace: fix memslot assignment
Date: Thu, 31 Jul 2008 14:53:56 +0200	[thread overview]
Message-ID: <200807311453.56210.borntraeger@de.ibm.com> (raw)
In-Reply-To: <4891A0DD.5000503@qumranet.com>

Am Donnerstag, 31. Juli 2008 schrieb Avi Kivity:
> > +#if defined(__x86_64__) || defined(__i386__)
> > +#if defined(KVM_CAP_SET_TSS_ADDR)
> > +	if (ioctl(kvm->fd, KVM_CHECK_EXTENSION, KVM_CAP_SET_TSS_ADDR) > 0)
> >   
> 
> Should be <= here?

yes. But with the wrapper you suggest below its again >.

> 
> > +		i++;
> > +#else
> > +	i++;
> > +#endif
> > +#endif
> >   
> 
> Suggest a helper, kvm_supports_set_tss_addr(), to reduce further 
> braindamage.

Something like that? But then I get the following warning on non-x86:
libkvm.c:77: warning: 'kvm_supports_set_tss_addr' defined but not used

Should I mask the wrapper with config x86 as well?


---
 libkvm.c |   32 +++++++++++++++++---------------
 1 file changed, 17 insertions(+), 15 deletions(-)

Index: libkvm/libkvm.c
===================================================================
--- libkvm.orig/libkvm.c
+++ libkvm/libkvm.c
@@ -73,27 +73,29 @@ void init_slots(void)
 		slots[i].len = 0;
 }
 
+static int kvm_supports_set_tss_addr(kvm_context_t kvm)
+{
+#if defined(KVM_CAP_SET_TSS_ADDR)
+	if (ioctl(kvm->fd, KVM_CHECK_EXTENSION, KVM_CAP_SET_TSS_ADDR) > 0)
+		return 1;
+#endif
+	return 0;
+}
+
 int get_free_slot(kvm_context_t kvm)
 {
 	int i;
-	int tss_ext;
-
-#if defined(KVM_CAP_SET_TSS_ADDR) && !defined(__s390__)
-	tss_ext = ioctl(kvm->fd, KVM_CHECK_EXTENSION, KVM_CAP_SET_TSS_ADDR);
-#else
-	tss_ext = 0;
-#endif
 
 	/*
-	 * on older kernels where the set tss ioctl is not supprted we must save
-	 * slot 0 to hold the extended memory, as the vmx will use the last 3
-	 * pages of this slot.
+	 * on older x86 kernels where the set tss ioctl is not supported we
+	 * must save slot 0 to hold the extended memory, as the vmx will
+	 * use the last 3 pages of this slot.
 	 */
-	if (tss_ext > 0)
-		i = 0;
-	else
-		i = 1;
-
+#if defined(__x86_64__) || defined(__i386__)
+	i = !kvm_supports_set_tss_addr(kvm);
+#else
+	i = 0;
+#endif
 	for (; i < KVM_MAX_NUM_MEM_REGIONS; ++i)
 		if (!slots[i].len)
 			return i;





  parent reply	other threads:[~2008-07-31 12:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-25 15:38 [PATCH] kvm-userspace: fix memslot assignment Christian Borntraeger
2008-07-27  8:18 ` Avi Kivity
2008-07-28 16:55   ` Christian Borntraeger
2008-07-29 13:18     ` Avi Kivity
2008-07-31  8:01       ` Christian Borntraeger
2008-07-31 11:24         ` Avi Kivity
2008-07-31 12:03           ` Izik Eidos
2008-07-31 12:53           ` Christian Borntraeger [this message]
2008-07-31 13:00             ` Avi Kivity
2008-07-31 14:57               ` Christian Borntraeger

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=200807311453.56210.borntraeger@de.ibm.com \
    --to=borntraeger@de.ibm.com \
    --cc=avi@qumranet.com \
    --cc=cotte@de.ibm.com \
    --cc=ehrhardt@linux.vnet.ibm.com \
    --cc=izike@qumranet.com \
    --cc=kvm@vger.kernel.org \
    --cc=os@de.ibm.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