From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Juergen Gross <jgross@suse.com>, xen-devel@lists.xenproject.org
Cc: "Stefano Stabellini" <sstabellini@kernel.org>,
"Wei Liu" <wei.liu2@citrix.com>,
"Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>,
"George Dunlap" <George.Dunlap@eu.citrix.com>,
"Tim Deegan" <tim@xen.org>,
"Ian Jackson" <ian.jackson@eu.citrix.com>,
"Julien Grall" <julien.grall@arm.com>,
"Jan Beulich" <jbeulich@suse.com>,
"Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: [PATCH 1/3] xen: drop in_atomic()
Date: Wed, 22 May 2019 10:58:25 +0100 [thread overview]
Message-ID: <6250d30e-dd9a-4fa9-7934-1f90948d8dad@citrix.com> (raw)
In-Reply-To: <20190522094549.28397-2-jgross@suse.com>
On 22/05/2019 10:45, Juergen Gross wrote:
> Currently there is only one user of in_atomic(), and that is in an
> #ifdef 0 section. This has been so since Xen 4.1, so chances are
> rather slim we suddenly want to enable it again.
>
> Dropping in_atomic() will remove the last user of preempt_count()
> in non-debug builds enabling further optimizations.
>
> Signed-off-by: Juergen Gross <jgross@suse.com>
Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
This code has never been used and is obviously not doing anything useful.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Juergen Gross <jgross@suse.com>, <xen-devel@lists.xenproject.org>
Cc: "Stefano Stabellini" <sstabellini@kernel.org>,
"Wei Liu" <wei.liu2@citrix.com>,
"Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>,
"George Dunlap" <George.Dunlap@eu.citrix.com>,
"Tim Deegan" <tim@xen.org>,
"Ian Jackson" <ian.jackson@eu.citrix.com>,
"Julien Grall" <julien.grall@arm.com>,
"Jan Beulich" <jbeulich@suse.com>,
"Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: [Xen-devel] [PATCH 1/3] xen: drop in_atomic()
Date: Wed, 22 May 2019 10:58:25 +0100 [thread overview]
Message-ID: <6250d30e-dd9a-4fa9-7934-1f90948d8dad@citrix.com> (raw)
Message-ID: <20190522095825.7EWAF1s_3s62povTr08foUDX_0DX4cT3OIN2FyQTVno@z> (raw)
In-Reply-To: <20190522094549.28397-2-jgross@suse.com>
On 22/05/2019 10:45, Juergen Gross wrote:
> Currently there is only one user of in_atomic(), and that is in an
> #ifdef 0 section. This has been so since Xen 4.1, so chances are
> rather slim we suddenly want to enable it again.
>
> Dropping in_atomic() will remove the last user of preempt_count()
> in non-debug builds enabling further optimizations.
>
> Signed-off-by: Juergen Gross <jgross@suse.com>
Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
This code has never been used and is obviously not doing anything useful.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-05-22 9:58 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-22 9:45 [PATCH 0/3] tune preempt_[dis|en]able() Juergen Gross
2019-05-22 9:45 ` [Xen-devel] " Juergen Gross
2019-05-22 9:45 ` [PATCH 1/3] xen: drop in_atomic() Juergen Gross
2019-05-22 9:45 ` [Xen-devel] " Juergen Gross
2019-05-22 9:58 ` Andrew Cooper [this message]
2019-05-22 9:58 ` Andrew Cooper
2019-05-22 10:10 ` Jan Beulich
2019-05-22 10:10 ` [Xen-devel] " Jan Beulich
2019-05-24 5:41 ` Juergen Gross
2019-05-24 5:41 ` [Xen-devel] " Juergen Gross
2019-05-24 6:38 ` Jan Beulich
2019-05-24 6:38 ` [Xen-devel] " Jan Beulich
2019-05-24 8:34 ` Juergen Gross
2019-05-24 8:34 ` [Xen-devel] " Juergen Gross
2019-05-24 8:39 ` Jan Beulich
2019-05-24 8:39 ` [Xen-devel] " Jan Beulich
2019-05-24 12:30 ` Andrew Cooper
2019-05-24 12:30 ` [Xen-devel] " Andrew Cooper
2019-05-24 12:35 ` Jan Beulich
2019-05-24 12:35 ` [Xen-devel] " Jan Beulich
[not found] ` <5CE52014020000780023147E@suse.com>
2019-05-22 10:19 ` Juergen Gross
2019-05-22 10:19 ` [Xen-devel] " Juergen Gross
2019-05-22 12:34 ` Jan Beulich
2019-05-22 12:34 ` [Xen-devel] " Jan Beulich
2019-05-22 9:45 ` [PATCH 2/3] xen: drop preempt_count() for non-debug builds Juergen Gross
2019-05-22 9:45 ` [Xen-devel] " Juergen Gross
2019-05-22 10:00 ` Andrew Cooper
2019-05-22 10:00 ` [Xen-devel] " Andrew Cooper
2019-05-22 10:17 ` Juergen Gross
2019-05-22 10:17 ` [Xen-devel] " Juergen Gross
2019-05-22 10:18 ` Jan Beulich
2019-05-22 10:18 ` [Xen-devel] " Jan Beulich
2019-05-22 10:39 ` Andrew Cooper
2019-05-22 10:39 ` [Xen-devel] " Andrew Cooper
2019-05-22 10:12 ` Jan Beulich
2019-05-22 10:12 ` [Xen-devel] " Jan Beulich
[not found] ` <5CE5207A0200007800231481@suse.com>
2019-05-22 10:17 ` Juergen Gross
2019-05-22 10:17 ` [Xen-devel] " Juergen Gross
2019-05-22 9:45 ` [PATCH 3/3] xen: build common/preempt.c only with CONFIG_DEBUG Juergen Gross
2019-05-22 9:45 ` [Xen-devel] " Juergen Gross
2019-05-22 13:01 [PATCH 1/3] xen: drop in_atomic() Juergen Gross
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=6250d30e-dd9a-4fa9-7934-1f90948d8dad@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=jgross@suse.com \
--cc=julien.grall@arm.com \
--cc=konrad.wilk@oracle.com \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=tim@xen.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).