qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: QEMU Developers <qemu-devel@nongnu.org>
Cc: Marcelo Tosatti <mtosatti@redhat.com>, Avi Kivity <avi@redhat.com>
Subject: [Qemu-devel] [PATCH] QEMU-KVM missing bits for E820 handling.
Date: Tue, 09 Mar 2010 18:24:58 +0100	[thread overview]
Message-ID: <4B96846A.4080003@redhat.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 112 bytes --]

Hi,

This is the last piece needed for QEMU-KVM to match the changes that
went into upstream QEMU.

Cheers,
Jes

[-- Attachment #2: 0011-qemu-kvm-e820-missing-bits.patch --]
[-- Type: text/plain, Size: 849 bytes --]

Use qemu-cfg to provide the BIOS with an optional table of e820 entries.

The missing bits for qemu-kvm.git to match what qemu does.

Signed-off-by: Jes Sorensen <Jes.Sorensen@redhat.com>

---
 qemu-kvm-x86.c |    7 +++++++
 1 file changed, 7 insertions(+)

Index: qemu-kvm/qemu-kvm-x86.c
===================================================================
--- qemu-kvm.orig/qemu-kvm-x86.c
+++ qemu-kvm/qemu-kvm-x86.c
@@ -37,6 +37,13 @@ int kvm_set_tss_addr(kvm_context_t kvm, 
 {
 #ifdef KVM_CAP_SET_TSS_ADDR
 	int r;
+        /*
+         * Tell fw_cfg to notify the BIOS to reserve the range.
+         */
+        if (e820_add_entry(addr, 0x4000, E820_RESERVED) < 0) {
+            perror("e820_add_entry() table is full");
+            exit(1);
+        }
 
 	r = kvm_ioctl(kvm_state, KVM_CHECK_EXTENSION, KVM_CAP_SET_TSS_ADDR);
 	if (r > 0) {

             reply	other threads:[~2010-03-09 17:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-09 17:24 Jes Sorensen [this message]
2010-03-11 12:35 ` [Qemu-devel] Re: [PATCH] QEMU-KVM missing bits for E820 handling 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=4B96846A.4080003@redhat.com \
    --to=jes.sorensen@redhat.com \
    --cc=avi@redhat.com \
    --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).