From: Steven Rostedt <srostedt@redhat.com>
To: virtualization@lists.osdl.org
Cc: Chris Wright <chrisw@sous-sol.org>
Subject: [RFC/PATCH PV_OPS X86_64 00/17] Paravirt_ops for x86_64
Date: Thu, 08 Mar 2007 00:53:57 -0500 [thread overview]
Message-ID: <45EFA4F5.1020001@redhat.com> (raw)
Hi all,
Glauber and I have been playing around with getting paravirt ops working
on the x86_64. We have our own version of lguest running there too.
We have lguest64 running up to console_init, and then it takes an
interrupt storm. I'll be posting those patches tomorrow.
Glauber and I have been sharing a git repo that isn't open to the public.
(we don't want people to see how crappy our stuff is yet ;)
Well, it's still kind of crappy, but it's starting to work. So I spent
today, pulling out patches related only to paravirt ops from our git
repo, and separating them to be readable. Well, here they are.
Tomorrow, I'll post what we got for lguest64 running.
Thanks!
-- Steve
--
next reply other threads:[~2007-03-08 5:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-08 5:53 Steven Rostedt [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-03-08 6:01 [RFC/PATCH PV_OPS X86_64 00/17] Paravirt_ops for x86_64 Steven Rostedt
2007-03-08 6:47 ` Chris Wright
2007-03-08 13:05 ` Steven Rostedt
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=45EFA4F5.1020001@redhat.com \
--to=srostedt@redhat.com \
--cc=chrisw@sous-sol.org \
--cc=virtualization@lists.osdl.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).