From: Shaohua Li <shli@fb.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
X86 ML <x86@kernel.org>, <kernel-team@fb.com>,
"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@redhat.com>
Subject: Re: [PATCH 2/3] X86: add a generic API to let vdso code detect context switch
Date: Wed, 10 Dec 2014 11:41:52 -0800 [thread overview]
Message-ID: <20141210194152.GA14261@devbig257.prn2.facebook.com> (raw)
In-Reply-To: <CALCETrUTgpxB1D43tjtv9So6k4H0OXzLXGJateYZtZahGXd4Sw@mail.gmail.com>
On Wed, Dec 10, 2014 at 11:11:27AM -0800, Andy Lutomirski wrote:
> On Wed, Dec 10, 2014 at 10:51 AM, Shaohua Li <shli@fb.com> wrote:
> > On Wed, Dec 10, 2014 at 10:38:41AM -0800, Andy Lutomirski wrote:
> >> On Sun, Dec 7, 2014 at 7:03 PM, Shaohua Li <shli@fb.com> wrote:
> >> > vdso code can't disable preempt, so it can be preempted at any time.
> >> > This makes a challenge to implement specific features. This patch adds a
> >> > generic API to let vdso code detect context switch.
> >> >
> >> > With this patch, every cpu maintains a context switch count. The upper
> >> > bits of the count is the logical cpu id, so the count can't be identical
> >> > for any cpu. The low bits of the count will be increased for each
> >> > context switch. For a x86_64 cpu with 4096 cpus, the context switch will
> >> > be overflowed for 2^(64 - 12) context switch, which is a long time and can be
> >> > ignored. The change of the count in giving time can be used to detect if
> >> > context switch occurs.
> >>
> >> Why do you need those high bits? I don't understand how you could
> >> possibly confuse one cpu's count with another's unless you fail to
> >> make sure that you're reading the same address both times.
> >>
> >> That being said, I don't like this patch. I'm not sure I have a much
> >> better idea, though. More thoughts in the 0/0 email to follow.
> > the vdso code doesn't disable preemption, so it can be migrated between
> > cpus at any time, the usage is:
> >
> > get_countext_switch_count (in cpu A)
> > do_something (in cpu B)
> > get_countext_switch_count (in cpu C)
> >
> > The cpu A, B, C could be completely different. We want to make sure
> > there is no preemption here and we use the context switch count to judge
> > this. If the high bits is ignored, the context switch count could be
> > identical even A != C, then our judgement using the switch count is
> > wrong.
>
> Sure, but you could compare the cpu numbers, too.
Aha, makes sense.
Thanks,
Shaohua
next prev parent reply other threads:[~2014-12-10 19:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-08 3:03 [PATCH 1/3] X86: make VDSO data support multiple pages Shaohua Li
2014-12-08 3:03 ` [PATCH 2/3] X86: add a generic API to let vdso code detect context switch Shaohua Li
2014-12-10 18:38 ` Andy Lutomirski
2014-12-10 18:51 ` Shaohua Li
2014-12-10 19:11 ` Andy Lutomirski
2014-12-10 19:41 ` Shaohua Li [this message]
2014-12-08 3:03 ` [PATCH 3/3] X86: Add a thread cpu time implementation to vDSO Shaohua Li
2014-12-10 19:10 ` Andy Lutomirski
2014-12-10 21:57 ` Shaohua Li
2014-12-10 22:13 ` Andy Lutomirski
2014-12-10 22:56 ` Shaohua Li
2014-12-10 23:06 ` Andy Lutomirski
2014-12-11 6:36 ` Ingo Molnar
2014-12-15 18:36 ` Chris Mason
2014-12-15 18:55 ` Andy Lutomirski
2014-12-10 18:36 ` [PATCH 1/3] X86: make VDSO data support multiple pages Andy Lutomirski
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=20141210194152.GA14261@devbig257.prn2.facebook.com \
--to=shli@fb.com \
--cc=hpa@zytor.com \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox