From: Chris Wright <chrisw@sous-sol.org>
To: Glauber de Oliveira Costa <gcosta@redhat.com>
Cc: virtualization@lists.osdl.org
Subject: Re: [PATCH] x86_64 paravirt_ops port
Date: Mon, 8 Jan 2007 17:00:33 -0800 [thread overview]
Message-ID: <20070109010033.GD19575@sequoia.sous-sol.org> (raw)
In-Reply-To: <20070108140826.GA1624@redhat.com>
* Glauber de Oliveira Costa (gcosta@redhat.com) wrote:
> I've been working on a port of paravirt_ops for the x86_64 architectures
> for a couple of days. Here's the result so far. I'm posting it soon for
> early cooments. The more, the better.
Thanks a lot for getting this started Glauber. As Rusty mentioned,
we'll want to follow the no export paravirt_ops motion upstream
for x86_64 as well.
> Index: linux-2.6.19-quilt/arch/x86_64/kernel/entry.S
> ===================================================================
> --- linux-2.6.19-quilt.orig/arch/x86_64/kernel/entry.S
> +++ linux-2.6.19-quilt/arch/x86_64/kernel/entry.S
> @@ -1064,6 +1064,22 @@ KPROBE_ENTRY(int3)
> CFI_ENDPROC
> KPROBE_END(int3)
>
> +#ifdef CONFIG_PARAVIRT
> +ENTRY(native_iret)
> +1: iretq
> +.section __ex_table,"a"
> + .align 8
> + .quad 1b, bad_iret
> +.previous
> +ENDPROC(native_iret)
> +
> +ENTRY(native_irq_enable_sysexit)
> + sti
> + sysretq
> +ENDPROC(native_irq_enable_sysexit)
sysexit is legacy mode only
and I think we'll need a story for swapgs
prev parent reply other threads:[~2007-01-09 1:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-08 14:08 [PATCH] x86_64 paravirt_ops port Glauber de Oliveira Costa
2007-01-08 23:05 ` Rusty Russell
2007-01-09 11:14 ` Glauber de Oliveira Costa
2007-01-09 1:00 ` Chris Wright [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=20070109010033.GD19575@sequoia.sous-sol.org \
--to=chrisw@sous-sol.org \
--cc=gcosta@redhat.com \
--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).