From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: "Kamble,
Nitin A" <nitin.a.kamble-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel
<kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
"Yu,
Wilfred" <wilfred.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
"Mallick,
Asit K" <asit.k.mallick-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH] implement pop reg in x86_emulate
Date: Sun, 10 Jun 2007 10:47:24 +0300 [thread overview]
Message-ID: <466BAC8C.7070309@qumranet.com> (raw)
In-Reply-To: <1181254922.21568.16.camel-mpPvwfgnXtFHIUuj5cj4Omt3HXsI98Cx0E9HWUfgJXw@public.gmane.org>
Kamble, Nitin A wrote:
> Hi Avi,
> I am in the middle of implementing the big real support in the KVM
> now. I am trying to boot SuseLinux 10.1 on KVM, which uses extensive
> big real mode code in the boot loader. If you have any other targeted
> guests using big real mode do let me know.
> I have been working on my own private tree for a while. I sync it
> with the KVM tree every day. I have lots of debug code in the
> infrastructure part of the big-real mode support. Also I think I may
> need to extend/change it further to support more instructions. So I
> plan to hold the infrastructure patches for now. Meanwhile I have
> implemented emulation of the needed instructions. As it is well
> contained and should not affect any code path, this instruction
> implementation can go upstream right away,
> Attached is a patch for the "pop reg" instruction emulation. I will
> be sending more of such instruction emulation patches very soon, I
> just need to break them apart from my debug tree. Do provide me if you
> have any feedback on these. And once I get the big-real mode support
> working well enough, I will start cleaning the remaining code from
> debug statements, and start pushing that code in patches to you.
Great, fixing real mode is very important.
The patch looks ok, but it is whitespace-damaged. Please use
scripts/checkpatch.pl to check patches before sending. It is also in
dos file format (crlf).
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
prev parent reply other threads:[~2007-06-10 7:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-07 22:22 [PATCH] implement pop reg in x86_emulate Kamble, Nitin A
[not found] ` <1181254922.21568.16.camel-mpPvwfgnXtFHIUuj5cj4Omt3HXsI98Cx0E9HWUfgJXw@public.gmane.org>
2007-06-08 3:52 ` H. Peter Anvin
[not found] ` <4668D280.3000009-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>
2007-06-08 17:43 ` Kamble, Nitin A
[not found] ` <1181324614.28454.9.camel-mpPvwfgnXtFHIUuj5cj4Omt3HXsI98Cx0E9HWUfgJXw@public.gmane.org>
2007-06-08 17:50 ` H. Peter Anvin
[not found] ` <466996D5.5070608-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>
2007-06-08 17:59 ` Kamble, Nitin A
[not found] ` <5461330FA59EDB46BE9AB8AAF2C431AD045D1A15-1a9uaKK1+wJcIJlls4ac1rfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-06-08 18:03 ` H. Peter Anvin
2007-06-10 7:47 ` Avi Kivity [this message]
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=466BAC8C.7070309@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=asit.k.mallick-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=nitin.a.kamble-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=wilfred.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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