From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: Stephen Hemminger <sthemmin@microsoft.com>
Cc: Haiyang Zhang <haiyangz@microsoft.com>,
"x86@kernel.org" <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Andy Lutomirski <luto@amacapital.net>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
Thomas Gleixner <tglx@linutronix.de>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>
Subject: Re: [PATCH 2/2] x86/vdso: Add VCLOCK_HVCLOCK vDSO clock read method
Date: Fri, 10 Feb 2017 13:25:36 +0100 [thread overview]
Message-ID: <87d1eqqlkv.fsf@vitty.brq.redhat.com> (raw)
In-Reply-To: <BLUPR0301MB20986D17696C3E658D511FACCC450@BLUPR0301MB2098.namprd03.prod.outlook.com> (Stephen Hemminger's message of "Thu, 9 Feb 2017 18:27:27 +0000")
Stephen Hemminger <sthemmin@microsoft.com> writes:
> Why not use existing seqlock's?
>
To be honest I don't quite understand how we could use it -- the
sequence locking here is done against the page updated by the
hypersior, we're not creating new structures (so I don't understand how
we could use struct seqcount which we don't have) but I may be
misunderstanding something.
BTW, I just occured to me that I should've probably put the TSC reading
code to mshyperv.h and use it from both vDSO and read_hv_clock_tsc() --
what do you thing?
[snip]
--
Vitaly
WARNING: multiple messages have this Message-ID (diff)
From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: Stephen Hemminger <sthemmin@microsoft.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
"x86\@kernel.org" <x86@kernel.org>,
Andy Lutomirski <luto@amacapital.net>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
"KY Srinivasan" <kys@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
Dexuan Cui <decui@microsoft.com>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devel\@linuxdriverproject.org" <devel@linuxdriverproject.org>,
"virtualization\@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>
Subject: Re: [PATCH 2/2] x86/vdso: Add VCLOCK_HVCLOCK vDSO clock read method
Date: Fri, 10 Feb 2017 13:25:36 +0100 [thread overview]
Message-ID: <87d1eqqlkv.fsf@vitty.brq.redhat.com> (raw)
In-Reply-To: <BLUPR0301MB20986D17696C3E658D511FACCC450@BLUPR0301MB2098.namprd03.prod.outlook.com> (Stephen Hemminger's message of "Thu, 9 Feb 2017 18:27:27 +0000")
Stephen Hemminger <sthemmin@microsoft.com> writes:
> Why not use existing seqlock's?
>
To be honest I don't quite understand how we could use it -- the
sequence locking here is done against the page updated by the
hypersior, we're not creating new structures (so I don't understand how
we could use struct seqcount which we don't have) but I may be
misunderstanding something.
BTW, I just occured to me that I should've probably put the TSC reading
code to mshyperv.h and use it from both vDSO and read_hv_clock_tsc() --
what do you thing?
[snip]
--
Vitaly
next prev parent reply other threads:[~2017-02-10 12:25 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 14:10 [PATCH 0/2] x86/vdso: Add Hyper-V TSC page clocksource support Vitaly Kuznetsov
2017-02-09 14:10 ` [PATCH 1/2] hyperv: implement hv_get_tsc_page() Vitaly Kuznetsov
2017-02-09 14:10 ` Vitaly Kuznetsov
2017-02-09 18:24 ` Stephen Hemminger via Virtualization
2017-02-09 18:24 ` Stephen Hemminger
2017-02-09 20:14 ` Thomas Gleixner
2017-02-09 20:14 ` Thomas Gleixner
2017-02-09 23:17 ` Stephen Hemminger
2017-02-09 23:17 ` Stephen Hemminger
2017-02-09 14:10 ` [PATCH 2/2] x86/vdso: Add VCLOCK_HVCLOCK vDSO clock read method Vitaly Kuznetsov
2017-02-09 17:08 ` Thomas Gleixner
2017-02-09 17:08 ` Thomas Gleixner
2017-02-09 18:27 ` Stephen Hemminger via Virtualization
2017-02-09 18:27 ` Stephen Hemminger
2017-02-10 12:25 ` Vitaly Kuznetsov [this message]
2017-02-10 12:25 ` Vitaly Kuznetsov
2017-02-10 12:28 ` Thomas Gleixner
2017-02-10 12:28 ` Thomas Gleixner
2017-02-10 16:31 ` Stephen Hemminger via Virtualization
2017-02-10 16:31 ` Stephen Hemminger
2017-02-10 18:01 ` Thomas Gleixner
2017-02-10 18:01 ` Thomas Gleixner
2017-02-13 7:49 ` Dexuan Cui via Virtualization
2017-02-13 7:49 ` Dexuan Cui
2017-02-13 9:27 ` Thomas Gleixner
2017-02-13 9:27 ` Thomas Gleixner
2017-02-13 19:06 ` Andy Lutomirski
2017-02-13 19:06 ` Andy Lutomirski
2017-02-13 19:28 ` Thomas Gleixner
2017-02-13 19:28 ` Thomas Gleixner
2017-02-09 20:45 ` KY Srinivasan via Virtualization
2017-02-09 20:45 ` KY Srinivasan
2017-02-09 22:55 ` Andy Lutomirski
2017-02-09 22:55 ` Andy Lutomirski
2017-02-09 23:15 ` Stephen Hemminger
2017-02-09 23:15 ` Stephen Hemminger
2017-02-10 12:15 ` Vitaly Kuznetsov
2017-02-10 12:15 ` Vitaly Kuznetsov
2017-02-10 11:06 ` Vitaly Kuznetsov
2017-02-10 11:06 ` Vitaly Kuznetsov
2017-02-10 11:15 ` Thomas Gleixner
2017-02-10 11:15 ` Thomas Gleixner
2017-02-09 14:10 ` Vitaly Kuznetsov
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=87d1eqqlkv.fsf@vitty.brq.redhat.com \
--to=vkuznets@redhat.com \
--cc=devel@linuxdriverproject.org \
--cc=haiyangz@microsoft.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@redhat.com \
--cc=sthemmin@microsoft.com \
--cc=tglx@linutronix.de \
--cc=virtualization@lists.linux-foundation.org \
--cc=x86@kernel.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.