From: "Jianyong Wu (Arm Technology China)" <Jianyong.Wu@arm.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
Marc Zyngier <maz@kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"yangbo.lu@nxp.com" <yangbo.lu@nxp.com>,
"john.stultz@linaro.org" <john.stultz@linaro.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"sean.j.christopherson@intel.com"
<sean.j.christopherson@intel.com>,
"richardcochran@gmail.com" <richardcochran@gmail.com>,
Mark Rutland <Mark.Rutland@arm.com>,
Will Deacon <Will.Deacon@arm.com>,
Suzuki Poulose <Suzuki.Poulose@arm.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
Steve Capper <Steve.Capper@arm.com>,
"Kaly Xin (Arm Technology China)" <Kaly.Xin@arm.com>,
"Justin He (Arm Technology China)" <Justin.He@arm.com>,
nd <nd@arm.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: RE: [RFC PATCH v3 4/6] psci: Add hvc call service for ptp_kvm.
Date: Wed, 9 Oct 2019 08:18:47 +0000 [thread overview]
Message-ID: <HE1PR0801MB1676B1AD68544561403C3196F4950@HE1PR0801MB1676.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <1cc145ca-1af2-d46f-d530-0ae434005f0b@redhat.com>
Hi Paolo,
> -----Original Message-----
> From: Paolo Bonzini <pbonzini@redhat.com>
> Sent: Wednesday, October 9, 2019 2:36 PM
> To: Jianyong Wu (Arm Technology China) <Jianyong.Wu@arm.com>; Marc
> Zyngier <maz@kernel.org>; netdev@vger.kernel.org; yangbo.lu@nxp.com;
> john.stultz@linaro.org; tglx@linutronix.de; sean.j.christopherson@intel.com;
> richardcochran@gmail.com; Mark Rutland <Mark.Rutland@arm.com>; Will
> Deacon <Will.Deacon@arm.com>; Suzuki Poulose
> <Suzuki.Poulose@arm.com>
> Cc: linux-kernel@vger.kernel.org; kvm@vger.kernel.org; Steve Capper
> <Steve.Capper@arm.com>; Kaly Xin (Arm Technology China)
> <Kaly.Xin@arm.com>; Justin He (Arm Technology China)
> <Justin.He@arm.com>; nd <nd@arm.com>; linux-arm-
> kernel@lists.infradead.org
> Subject: Re: [RFC PATCH v3 4/6] psci: Add hvc call service for ptp_kvm.
>
> On 09/10/19 07:21, Jianyong Wu (Arm Technology China) wrote:
> > As ptp_kvm clock has fixed to arm arch system counter in patch set v4,
> > we need check if the current clocksource is system counter when return
> > clock cycle in host, so a helper needed to return the current
> > clocksource. Could I add this helper in next patch set?
>
> You don't need a helper. You need to return the ARM arch counter
> clocksource in the struct system_counterval_t that you return.
> get_device_system_crosststamp will then check that the clocksource
> matches the active one.
>
We must ensure both of the host and guest using the same clocksource.
get_device_system_crosststamp will check the clocksource of guest and we also need check
the clocksource in host, and struct type can't be transferred from host to guest using arm hypercall.
now we lack of a mechanism to check the current clocksource. I think this will be useful if we add one.
Thanks
Jianyong Wu
> Paolo
next prev parent reply other threads:[~2019-10-09 8:19 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-18 8:07 [RFC PATCH v3 0/6] Enable ptp_kvm for arm64 Jianyong Wu
2019-09-18 8:07 ` [RFC PATCH v3 1/6] psci: Export psci_ops.conduit symbol as modules will use it Jianyong Wu
2019-09-18 8:07 ` [RFC PATCH v3 2/6] ptp: Reorganize ptp_kvm modules to make it arch-independent Jianyong Wu
2019-09-18 8:07 ` [RFC PATCH v3 3/6] timekeeping: Expose API allowing retrival of current clocksource and counter value Jianyong Wu
2019-09-18 8:29 ` Paolo Bonzini
2019-09-18 8:07 ` [RFC PATCH v3 4/6] psci: Add hvc call service for ptp_kvm Jianyong Wu
2019-09-18 8:25 ` Paolo Bonzini
2019-09-18 9:57 ` Jianyong Wu (Arm Technology China)
2019-09-18 10:23 ` Paolo Bonzini
2019-09-19 9:46 ` Jianyong Wu (Arm Technology China)
2019-09-19 11:07 ` Paolo Bonzini
2019-09-19 11:39 ` Marc Zyngier
2019-09-19 12:13 ` Paolo Bonzini
2019-09-23 3:19 ` Jianyong Wu (Arm Technology China)
2019-10-09 5:21 ` Jianyong Wu (Arm Technology China)
2019-10-09 6:36 ` Paolo Bonzini
2019-10-09 8:18 ` Jianyong Wu (Arm Technology China) [this message]
2019-10-09 9:13 ` Paolo Bonzini
2019-10-09 16:05 ` John Stultz
2019-10-09 20:56 ` Paolo Bonzini
2019-10-14 5:50 ` Jianyong Wu (Arm Technology China)
2019-10-14 6:58 ` Paolo Bonzini
2019-09-23 4:57 ` Jianyong Wu (Arm Technology China)
2019-09-24 14:20 ` Paolo Bonzini
2019-09-25 10:27 ` Jianyong Wu (Arm Technology China)
2019-09-18 8:07 ` [RFC PATCH v3 5/6] ptp: arm64: Enable ptp_kvm for arm64 Jianyong Wu
2019-09-18 8:07 ` [RFC PATCH v3 6/6] kvm: arm64: Add capability check extension for ptp_kvm Jianyong Wu
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=HE1PR0801MB1676B1AD68544561403C3196F4950@HE1PR0801MB1676.eurprd08.prod.outlook.com \
--to=jianyong.wu@arm.com \
--cc=Justin.He@arm.com \
--cc=Kaly.Xin@arm.com \
--cc=Mark.Rutland@arm.com \
--cc=Steve.Capper@arm.com \
--cc=Suzuki.Poulose@arm.com \
--cc=Will.Deacon@arm.com \
--cc=john.stultz@linaro.org \
--cc=kvm@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=nd@arm.com \
--cc=netdev@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=richardcochran@gmail.com \
--cc=sean.j.christopherson@intel.com \
--cc=tglx@linutronix.de \
--cc=yangbo.lu@nxp.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 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).