[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] fpu_taskswitch adjustment proposal
- To: Jan Beulich <JBeulich@xxxxxxxx>
- From: Keir Fraser <keir@xxxxxxx>
- Date: Mon, 18 Jun 2012 14:59:15 +0100
- Cc: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxx>
- Delivery-date: Mon, 18 Jun 2012 13:59:52 +0000
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:user-agent:date:subject:from:to:cc:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; bh=AaPuNpdkyfY5wFfjdeJ4ZCce2LmLnUWOwpydynOfAF8=; b=DET5BqrVcQYse9w8YVxiP5afF9bjD9bFHovxVgSMCSTNbryIGMcUY/+Yf48ceWKWrW cdYZegnH2dufVGmwV0Z6k/Bc5/kWH1Vph7nOn9RQkSZf7F6GgNSF4nFgmmPjOKPF/7oF ow4jRE6vlkUika9b95e9MoS13j1ohrk7L6X9bzrYAlCXZPQ5G0urrAcw6Uo/9LGdXoq/ kvA7M+JLNiD7SCVV3cxl3BGnY3bvu/19p9PWZ0P/5vJXp1PZhvapSvwLGFfuCTpSkVnG IGPdqISLVhI27UjEohqmTpY0SHvXjSaOn/L7P0TZDeqC+VXuMZdUBo8YnQA4huSRDCWk xuoA==
- List-id: Xen developer discussion <xen-devel.lists.xen.org>
- Thread-index: Ac1NWou2yJlDpUZuz0qUu8ZOhgNVKg==
- Thread-topic: [Xen-devel] fpu_taskswitch adjustment proposal
On 18/06/2012 13:45, "Jan Beulich" <JBeulich@xxxxxxxx> wrote:
>> Wouldn't it be hidden entirely behind pv_ops hooks and within Xen-specific
>> SSE save/restore code? I suppose you'd need to statically allocate the
>> per-cpu space for tracking the CR0.TS state... But overall it seems it will
>> be of little/no concern to other kernel maintainers?
>
> The #NM handler part wouldn't afaict. Everything else indeed
> ought to be restricted to the functions backing paravirt.h's clts()
> and write_cr0().
Yes, the #NM handler might need extra treatment. Perhaps we could install
our own #NM wrapper around the kernel's generic handler, which first clears
the saved CR0.TS flag. Then on clts() in the generic handler, our paravirt
clts() would see the flag is already clear and do no hypercall.
-- Keir
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel