From: Olaf Hering <olaf@aepfle.de>
To: Jan Beulich <JBeulich@suse.com>
Cc: Tim Deegan <tim@xen.org>,
Stefano Stabellini <sstabellini@kernel.org>,
Wei Liu <wei.liu2@citrix.com>,
George Dunlap <George.Dunlap@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Marek Marczykowski <marmarek@invisiblethingslab.com>,
xen-devel@lists.xen.org, Julien Grall <julien.grall@arm.com>
Subject: Re: [PATCH v9] new config option vtsc_tolerance_khz to avoid TSC emulation
Date: Thu, 7 Jun 2018 15:47:43 +0200 [thread overview]
Message-ID: <20180607154743.0c8a808e.olaf@aepfle.de> (raw)
In-Reply-To: <5B1933AE02000078001C91DA@prv1-mh.provo.novell.com>
[-- Attachment #1.1: Type: text/plain, Size: 594 bytes --]
Am Thu, 07 Jun 2018 07:31:26 -0600
schrieb "Jan Beulich" <JBeulich@suse.com>:
> Hmm, I find this description concerning. Is the field reliably zero when
> coming from older Xen, or is it not?
It depends on how old.
If the other sending side has write_tsc_info from 4.6+, then _res1 is zero.
If it is older, the XC_SAVE_ID_TSC_INFO is eventually not handled anymore.
At least I could not find the relevant code, even in staging-4.6.
But then, it is unlikely that migration from 4.5 to 4.6 did not work.
Also, in general the input comes from "remote". So it is untrusted.
Olaf
[-- Attachment #1.2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 157 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-06-07 13:47 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-07 13:08 [PATCH v9] new config option vtsc_tolerance_khz to avoid TSC emulation Olaf Hering
2018-06-07 13:31 ` Jan Beulich
2018-06-07 13:47 ` Olaf Hering [this message]
2018-06-07 14:44 ` Jan Beulich
2018-06-07 14:49 ` Olaf Hering
2018-06-07 14:55 ` Jan Beulich
2018-06-07 21:05 ` Olaf Hering
2018-06-26 17:11 ` Olaf Hering
2018-08-01 16:17 ` Olaf Hering
2018-09-13 7:39 ` Olaf Hering
2018-09-28 13:50 ` Olaf Hering
2018-10-01 10:52 ` Ian Jackson
2018-10-01 11:25 ` Jan Beulich
2018-10-01 13:38 ` George Dunlap
2018-10-01 14:00 ` Jan Beulich
2018-10-01 14:25 ` George Dunlap
2018-10-01 16:01 ` Wei Liu
2018-10-01 12:39 ` Andrew Cooper
2018-10-01 13:24 ` [PATCH v9] new config option vtsc_tolerance_khz to avoid TSC emulation [and 1 more messages] Ian Jackson
2018-10-01 13:58 ` Andrew Cooper
2018-10-01 13:29 ` [PATCH v9] new config option vtsc_tolerance_khz to avoid TSC emulation Jan Beulich
2018-10-01 15:17 ` Andrew Cooper
2018-10-01 15:28 ` Jan Beulich
2018-10-09 16:42 ` Olaf Hering
2018-11-29 13:21 ` Olaf Hering
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=20180607154743.0c8a808e.olaf@aepfle.de \
--to=olaf@aepfle.de \
--cc=George.Dunlap@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=julien.grall@arm.com \
--cc=marmarek@invisiblethingslab.com \
--cc=sstabellini@kernel.org \
--cc=tim@xen.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.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.