All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>, kvm <kvm@vger.kernel.org>,
	Anthony Liguori <aliguori@us.ibm.com>
Subject: Re: [PATCH 1/2] qemu-kvm: extboot: Keep variables in RAM
Date: Mon, 22 Feb 2010 11:40:03 +0200	[thread overview]
Message-ID: <4B8250F3.6050302@redhat.com> (raw)
In-Reply-To: <4B7D6725.1090202@siemens.com>

On 02/18/2010 06:13 PM, Jan Kiszka wrote:
> Instead of saving the old INT 0x13 and 0x19 handlers in ROM which fails
> under QEMU as it enforces protection, keep them in spare vectors of the
> interrupt table, namely INT 0x80 and 0x81.
>
>    

Applied both, thanks.

> Don't forget to update extboot.bin after merging both patches.
>    

We don't carry a precompiled binary (well, we have 
qemu/pc-bios/extboot.bin, but that's bogus and I've removed it).

-- 
error compiling committee.c: too many arguments to function


  parent reply	other threads:[~2010-02-22  9:40 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-18 16:13 [PATCH 1/2] qemu-kvm: extboot: Keep variables in RAM Jan Kiszka
2010-02-18 20:27 ` Anthony Liguori
2010-02-18 22:56   ` H. Peter Anvin
2010-02-19 10:06     ` Jan Kiszka
2010-02-19 16:50       ` H. Peter Anvin
2010-02-19 17:03         ` Jan Kiszka
2010-02-19 17:24           ` H. Peter Anvin
2010-02-19 17:44             ` Jan Kiszka
2010-02-19 18:10           ` Anthony Liguori
2010-02-19 18:17             ` Jan Kiszka
2010-02-19 19:37               ` H. Peter Anvin
2010-02-20  3:21                 ` Kevin O'Connor
2010-02-22 10:03               ` Stefan Hajnoczi
     [not found]                 ` <4B82DE3F.5090306@linux.intel.com>
2010-02-23  9:30                   ` Stefan Hajnoczi
2010-02-22  9:40 ` Avi Kivity [this message]
2010-02-22  9:59   ` Jan Kiszka
2010-02-22 10:03     ` Jan Kiszka
2010-02-22 11:02     ` Avi Kivity
2010-04-06  8:50   ` Jan Kiszka

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=4B8250F3.6050302@redhat.com \
    --to=avi@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=jan.kiszka@siemens.com \
    --cc=kvm@vger.kernel.org \
    --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 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.