From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Andrew Lutomirski <luto@mit.edu>
Cc: jeremy@goop.org, xen-devel@lists.xensource.com, x86@kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
virtualization@lists.linux-foundation.org, keir.xen@gmail.com
Subject: Re: [Xen-devel] Re: [PATCH 0/5] Collected vdso/vsyscall fixes for 3.1
Date: Wed, 27 Jul 2011 12:29:57 -0400 [thread overview]
Message-ID: <20110727162956.GA16931@dumpdata.com> (raw)
In-Reply-To: <CAObL_7FncQ7DdNf2igFZW=ZzPFQLO3Vvp1c_y5EajA_KTt8iOg@mail.gmail.com>
> 400c8d: c4 e1 f3 2a c8 vcvtsi2sd %rax,%xmm1,%xmm1
>
> which is unlikely to work on AMD unless you're the lucky owner of a
> prerelease Bulldozer chip. I
>
> I bet if you pull a new copy or remove -mavx from Makefile it will
> work. I got a grossly hacked-up Xen domU booted and everything seems
> to work.
Ok.
>
> (Testing native kernels is really fun with qemu-kvm -kernel <image>
> -initrd <my silly initramfs>. But Xen doesn't seem to support that.)
You mean running Xen within QEMU? It does, but you need to use a multiboot
loader and QEMU does not seem to support that. You can create an
.iso image with isolinux that loads mboot.c32 for that.
If you want to use qemu like that in Xen environment you can do it too.
Just need the upstream version and use -M xenpv
next prev parent reply other threads:[~2011-07-27 16:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-27 3:20 [PATCH 0/5] Collected vdso/vsyscall fixes for 3.1 Andy Lutomirski
2011-07-27 3:20 ` [PATCH 1/5] x86-64: Pad vDSO to a page boundary Andy Lutomirski
2011-07-27 3:20 ` [PATCH 2/5] x86-64: Move the "user" vsyscall segment out of the data segment Andy Lutomirski
2011-07-27 3:20 ` [PATCH 3/5] x86-64: Work around gold bug 13023 Andy Lutomirski
2011-07-27 3:20 ` [PATCH 4/5] x86-64/xen: Enable the vvar mapping Andy Lutomirski
2011-07-27 13:06 ` Konrad Rzeszutek Wilk
2011-07-27 13:48 ` Andrew Lutomirski
2011-07-27 3:20 ` [PATCH 5/5] x86-64: Add user_64bit_mode paravirt op Andy Lutomirski
2011-07-27 17:24 ` Jeremy Fitzhardinge
2011-07-27 17:45 ` Andrew Lutomirski
2011-07-27 12:59 ` [PATCH 0/5] Collected vdso/vsyscall fixes for 3.1 Konrad Rzeszutek Wilk
2011-07-27 14:57 ` Konrad Rzeszutek Wilk
2011-07-27 15:04 ` Andrew Lutomirski
2011-07-27 15:30 ` Konrad Rzeszutek Wilk
2011-07-27 15:34 ` Andrew Lutomirski
2011-07-27 15:43 ` Konrad Rzeszutek Wilk
2011-07-27 16:15 ` Andrew Lutomirski
2011-07-27 16:29 ` Konrad Rzeszutek Wilk [this message]
2011-07-27 16:58 ` [Xen-devel] " Konrad Rzeszutek Wilk
2011-07-27 17:05 ` Andrew Lutomirski
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=20110727162956.GA16931@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=jeremy@goop.org \
--cc=keir.xen@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@mit.edu \
--cc=virtualization@lists.linux-foundation.org \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xensource.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