From: Juergen Gross <juergen.gross@ts.fujitsu.com>
To: Jan Beulich <JBeulich@novell.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [Patch] continue_hypercall_on_cpu rework using tasklets
Date: Tue, 13 Apr 2010 15:49:52 +0200 [thread overview]
Message-ID: <4BC47680.60700@ts.fujitsu.com> (raw)
In-Reply-To: <4BC4908B020000780003A008@vpn.id2.novell.com>
Jan Beulich wrote:
>>>> Juergen Gross <juergen.gross@ts.fujitsu.com> 13.04.10 15:19 >>>
>> cpupools are using continue_hypercall_on_cpu, but this function is defined for
>> x86 only, not for ia64. I see 2 possible solutions:
>>
>> 1. make continue_hypercall_on_cpu available on ia64, too
>> 2. make cpupools a pure x86 feature
>
> Is there anything meaningful in the new code that's really x86-specific
> (i.e. can't the whole code chunk be moved to xen/common/)?
My main concern is the difference in the handling of schedule_tail. I just
can't tell how to change the ia64 variant to make it work correctly.
The other x86-specific part is the setting of the return register, but this
is rather easy doable by using an architecture specific macro.
Juergen
--
Juergen Gross Principal Developer Operating Systems
TSP ES&S SWE OS6 Telephone: +49 (0) 89 3222 2967
Fujitsu Technology Solutions e-mail: juergen.gross@ts.fujitsu.com
Domagkstr. 28 Internet: ts.fujitsu.com
D-80807 Muenchen Company details: ts.fujitsu.com/imprint.html
next prev parent reply other threads:[~2010-04-13 13:49 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-13 13:19 [Patch] continue_hypercall_on_cpu rework using tasklets Juergen Gross
2010-04-13 13:40 ` Jan Beulich
2010-04-13 13:49 ` Juergen Gross [this message]
2010-04-13 15:08 ` Keir Fraser
2010-04-14 6:54 ` Juergen Gross
2010-04-13 14:41 ` Keir Fraser
2010-04-14 4:26 ` Juergen Gross
2010-04-14 6:46 ` Keir Fraser
2010-04-14 6:58 ` Juergen Gross
2010-04-14 7:15 ` Keir Fraser
2010-04-14 7:25 ` Juergen Gross
2010-04-14 7:35 ` Keir Fraser
2010-04-14 8:04 ` Juergen Gross
2010-04-14 10:30 ` Keir Fraser
2010-04-15 6:31 ` Juergen Gross
2010-04-15 6:39 ` Keir Fraser
2010-04-15 7:57 ` Juergen Gross
2010-04-15 8:13 ` Keir Fraser
2010-04-15 8:22 ` Keir Fraser
2010-04-15 9:59 ` Jiang, Yunhong
2010-04-15 11:06 ` Keir Fraser
2010-04-15 11:22 ` Keir Fraser
2010-04-16 9:20 ` Yu, Ke
2010-04-16 17:51 ` Keir Fraser
2010-04-19 10:50 ` Keir Fraser
2010-04-19 12:04 ` Yu, Ke
2010-04-20 5:35 ` Wei, Gang
2010-04-20 12:51 ` Keir Fraser
2010-04-20 14:10 ` Wei, Gang
2010-04-21 6:47 ` Wei, Gang
2010-04-16 6:42 ` Jiang, Yunhong
2010-04-16 6:55 ` Juergen Gross
2010-04-16 8:30 ` Jiang, Yunhong
2010-04-16 7:13 ` Keir Fraser
2010-04-16 8:16 ` Jiang, Yunhong
2010-04-16 17:57 ` Keir Fraser
2010-04-19 5:53 ` Jiang, Yunhong
2010-04-19 6:48 ` Keir Fraser
2010-04-16 6:45 ` Jiang, Yunhong
2010-04-15 8:29 ` Juergen Gross
2010-04-15 9:08 ` Keir Fraser
-- strict thread matches above, loose matches on Subject: below --
2009-12-30 13:46 Juergen Gross
2009-12-30 13:57 ` Keir Fraser
2009-12-30 13:59 ` Juergen Gross
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=4BC47680.60700@ts.fujitsu.com \
--to=juergen.gross@ts.fujitsu.com \
--cc=JBeulich@novell.com \
--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 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.