From: Peter Zijlstra <peterz@infradead.org>
To: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
Cc: "linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
"Vineet.Gupta1@synopsys.com" <Vineet.Gupta1@synopsys.com>,
"linux-snps-arc@lists.infradead.org"
<linux-snps-arc@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: arc_usr_cmpxchg and preemption
Date: Thu, 15 Mar 2018 09:18:45 +0100 [thread overview]
Message-ID: <20180315081845.GS4064@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <1521059931.11552.51.camel@synopsys.com>
On Wed, Mar 14, 2018 at 08:38:53PM +0000, Alexey Brodkin wrote:
> > int sys_cmpxchg(u32 __user *user_ptr, u32 old, u32 new)
> > {
> > u32 val;
> > int ret;
> >
> > again:
> > ret = 0;
> >
> > preempt_disable();
> > val = get_user(user_ptr);
> > if (val == old)
> > ret = put_user(new, user_ptr);
> > preempt_enable();
> >
> > if (ret == -EFAULT) {
> > struct page *page;
> > ret = get_user_pages_fast((unsigned long)user_ptr, 1, 1, &page);
> > if (ret < 0)
> > return ret;
> > put_page(page);
> > goto again;
>
> I guess this jump we need to do only once, right?
Typically, yes. It is theoretically possible for the page to get
paged-out right after we do put_page() and before we do get/put_user(),
But if that happens the machine likely has bigger problems than having
to do this loop again.
FWIW, look at kernel/futex.c for working examples of this pattern, the
above was written purely from memory and could contain a fail or two ;-)
Also, it might make sense to stuff this implementation in some lib/ file
somewhere and make all platforms that need it use the same code, afaict
there really isn't anything platform specific to it.
WARNING: multiple messages have this Message-ID (diff)
From: Peter Zijlstra <peterz@infradead.org>
To: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
Cc: "Vineet.Gupta1@synopsys.com" <Vineet.Gupta1@synopsys.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
"linux-snps-arc@lists.infradead.org"
<linux-snps-arc@lists.infradead.org>
Subject: Re: arc_usr_cmpxchg and preemption
Date: Thu, 15 Mar 2018 09:18:45 +0100 [thread overview]
Message-ID: <20180315081845.GS4064@hirez.programming.kicks-ass.net> (raw)
Message-ID: <20180315081845.QUJVfSCRdb9Hx_lhmZvDfVrEdj-NvO46pcE93r-7k6A@z> (raw)
In-Reply-To: <1521059931.11552.51.camel@synopsys.com>
On Wed, Mar 14, 2018 at 08:38:53PM +0000, Alexey Brodkin wrote:
> > int sys_cmpxchg(u32 __user *user_ptr, u32 old, u32 new)
> > {
> > u32 val;
> > int ret;
> >
> > again:
> > ret = 0;
> >
> > preempt_disable();
> > val = get_user(user_ptr);
> > if (val == old)
> > ret = put_user(new, user_ptr);
> > preempt_enable();
> >
> > if (ret == -EFAULT) {
> > struct page *page;
> > ret = get_user_pages_fast((unsigned long)user_ptr, 1, 1, &page);
> > if (ret < 0)
> > return ret;
> > put_page(page);
> > goto again;
>
> I guess this jump we need to do only once, right?
Typically, yes. It is theoretically possible for the page to get
paged-out right after we do put_page() and before we do get/put_user(),
But if that happens the machine likely has bigger problems than having
to do this loop again.
FWIW, look at kernel/futex.c for working examples of this pattern, the
above was written purely from memory and could contain a fail or two ;-)
Also, it might make sense to stuff this implementation in some lib/ file
somewhere and make all platforms that need it use the same code, afaict
there really isn't anything platform specific to it.
WARNING: multiple messages have this Message-ID (diff)
From: peterz@infradead.org (Peter Zijlstra)
To: linux-snps-arc@lists.infradead.org
Subject: arc_usr_cmpxchg and preemption
Date: Thu, 15 Mar 2018 09:18:45 +0100 [thread overview]
Message-ID: <20180315081845.GS4064@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <1521059931.11552.51.camel@synopsys.com>
On Wed, Mar 14, 2018@08:38:53PM +0000, Alexey Brodkin wrote:
> > int sys_cmpxchg(u32 __user *user_ptr, u32 old, u32 new)
> > {
> > u32 val;
> > int ret;
> >
> > again:
> > ret = 0;
> >
> > preempt_disable();
> > val = get_user(user_ptr);
> > if (val == old)
> > ret = put_user(new, user_ptr);
> > preempt_enable();
> >
> > if (ret == -EFAULT) {
> > struct page *page;
> > ret = get_user_pages_fast((unsigned long)user_ptr, 1, 1, &page);
> > if (ret < 0)
> > return ret;
> > put_page(page);
> > goto again;
>
> I guess this jump we need to do only once, right?
Typically, yes. It is theoretically possible for the page to get
paged-out right after we do put_page() and before we do get/put_user(),
But if that happens the machine likely has bigger problems than having
to do this loop again.
FWIW, look at kernel/futex.c for working examples of this pattern, the
above was written purely from memory and could contain a fail or two ;-)
Also, it might make sense to stuff this implementation in some lib/ file
somewhere and make all platforms that need it use the same code, afaict
there really isn't anything platform specific to it.
next prev parent reply other threads:[~2018-03-15 8:18 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-14 16:36 arc_usr_cmpxchg and preemption Alexey Brodkin
2018-03-14 16:58 ` Vineet Gupta
2018-03-14 16:58 ` Vineet Gupta
2018-03-14 17:53 ` Peter Zijlstra
2018-03-14 17:53 ` Peter Zijlstra
2018-03-14 17:53 ` Peter Zijlstra
2018-03-14 18:20 ` Peter Zijlstra
2018-03-14 18:20 ` Peter Zijlstra
2018-03-14 18:20 ` Peter Zijlstra
2018-03-14 20:38 ` Alexey Brodkin
2018-03-14 20:38 ` Alexey Brodkin
2018-03-14 20:55 ` Vineet Gupta
2018-03-14 20:55 ` Vineet Gupta
2018-03-15 8:18 ` Peter Zijlstra [this message]
2018-03-15 8:18 ` Peter Zijlstra
2018-03-15 8:18 ` Peter Zijlstra
2018-03-15 9:12 ` Alexey Brodkin
2018-03-15 9:12 ` Alexey Brodkin
2018-03-15 11:28 ` Peter Zijlstra
2018-03-15 11:28 ` Peter Zijlstra
2018-03-15 11:28 ` Peter Zijlstra
2018-03-15 19:03 ` Alexey Brodkin
2018-03-15 19:03 ` Alexey Brodkin
2018-03-15 19:03 ` Alexey Brodkin
2018-03-16 7:55 ` Peter Zijlstra
2018-03-16 7:55 ` Peter Zijlstra
2018-03-16 7:55 ` Peter Zijlstra
2018-03-16 18:12 ` Max Filippov
2018-03-16 18:12 ` Max Filippov
2018-03-16 17:33 ` Alexey Brodkin
2018-03-16 17:33 ` Alexey Brodkin
2018-03-16 17:54 ` Vineet Gupta
2018-03-16 17:54 ` Vineet Gupta
2018-03-16 17:58 ` Peter Zijlstra
2018-03-16 17:58 ` Peter Zijlstra
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=20180315081845.GS4064@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=Alexey.Brodkin@synopsys.com \
--cc=Vineet.Gupta1@synopsys.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.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.