All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: Fouad Hilly <fouad.hilly@cloud.com>
Cc: "Roger Pau Monné" <roger.pau@citrix.com>,
	"Andrew Cooper" <andrew.cooper3@citrix.com>,
	"Wei Liu" <wl@xen.org>,
	"George Dunlap" <george.dunlap@citrix.com>,
	"Julien Grall" <julien@xen.org>,
	"Stefano Stabellini" <sstabellini@kernel.org>,
	"Paul Durrant" <paul@xen.org>,
	"Jun Nakajima" <jun.nakajima@intel.com>,
	"Kevin Tian" <kevin.tian@intel.com>,
	Xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH 0/3] X86/eager-fpu: Switch to eager fpu save/restore
Date: Tue, 5 Mar 2024 10:26:11 +0100	[thread overview]
Message-ID: <c1eb7340-aa11-476e-b2c6-bb8753d7edde@suse.com> (raw)
In-Reply-To: <20240304091307.2295344-1-fouad.hilly@cloud.com>

On 04.03.2024 10:13, Fouad Hilly wrote:
> X86 Xen will only eagerly switch FPU context in the scheduler.
> Xen itslef won't set CR0.TS other than for the purpose of servicing
> a PV guset.
> 
> Signed-off-by: Wei Liu <wei.liu2@citrix.com>
> Signed-off-by: Roger Pau Monné <roger.pau@citrix.com>
> Signed-off-by: Fouad Hilly <fouad.hilly@cloud.com>

Throughout replying to the series I got back "undeliverable" responses
for Wei's old address at Citrix (noticed only now when I looked at what
has accumulated again in my inbox in the meantime). Can you please avoid
having dead addresses in patch submissions?

Jan


      parent reply	other threads:[~2024-03-05  9:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-04  9:13 [PATCH 0/3] X86/eager-fpu: Switch to eager fpu save/restore Fouad Hilly
2024-03-04  9:13 ` [PATCH 1/3] x86: i387.c cleanup Fouad Hilly
2024-03-05  8:43   ` Jan Beulich
2024-03-04  9:13 ` [PATCH 2/3] x86: introduce xstate_zero Fouad Hilly
2024-03-05  9:06   ` Jan Beulich
2024-03-04  9:13 ` [PATCH 3/3] x86: switch to eager fpu save / restore Fouad Hilly
2024-03-05  9:22   ` Jan Beulich
2024-03-05  9:26 ` Jan Beulich [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=c1eb7340-aa11-476e-b2c6-bb8753d7edde@suse.com \
    --to=jbeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=fouad.hilly@cloud.com \
    --cc=george.dunlap@citrix.com \
    --cc=julien@xen.org \
    --cc=jun.nakajima@intel.com \
    --cc=kevin.tian@intel.com \
    --cc=paul@xen.org \
    --cc=roger.pau@citrix.com \
    --cc=sstabellini@kernel.org \
    --cc=wl@xen.org \
    --cc=xen-devel@lists.xenproject.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 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.