There is no more direct user of this macro; it is only used by
cc-ifversion.
Calling this macro is not efficient since it invokes the compiler to
get the compiler version. CONFIG_GCC_VERSION is already calculated in
the Kconfig stage, so Makefile can reuse it.
Here is a note about the slight diff
Hi Joel,
On Thu, 28 Feb 2019 22:26:11 -0500
Joel Fernandes wrote:
> On Fri, Mar 01, 2019 at 11:28:26AM +0900, Masami Hiramatsu wrote:
> > Hi Joel,
>
> Hi Masami,
>
> > On Thu, 28 Feb 2019 10:00:54 -0500
> > Joel Fernandes wrote:
> >
> > > > Hmm, isn't it easier to add kernel-headers package
Hi,
On 2/26/19 7:05 PM, Jeremy Linton wrote:
There are various reasons, including bencmarking, to disable spectrev2
mitigation on a machine. Provide a command-line to do so.
Signed-off-by: Jeremy Linton
Reviewed-by: Andre Przywara
Cheers,
Andre.
Cc: Jonathan Corbet
Cc: linux-doc@vger.ke
On Fri, Mar 1, 2019 at 12:06 AM Joel Fernandes wrote:
>
> On Thu, Feb 28, 2019 at 11:17:51AM +0900, Masahiro Yamada wrote:
> > Hi Joel,
> >
> >
> > On Thu, Feb 28, 2019 at 4:40 AM Joel Fernandes (Google)
> > wrote:
> > >
> > > Introduce in-kernel headers and other artifacts which are made availab
On Fri, Mar 01, 2019 at 11:28:26AM +0900, Masami Hiramatsu wrote:
> Hi Joel,
Hi Masami,
> On Thu, 28 Feb 2019 10:00:54 -0500
> Joel Fernandes wrote:
>
> > > Hmm, isn't it easier to add kernel-headers package on Android?
> >
> > I have already been down that road. In the Android ecosystem, the
Hi Joel,
On Thu, 28 Feb 2019 10:00:54 -0500
Joel Fernandes wrote:
> > Hmm, isn't it easier to add kernel-headers package on Android?
>
> I have already been down that road. In the Android ecosystem, the Android
> teams only provide a "userspace system image" which goes on the system
> partition
On Thu, Feb 28, 2019 at 09:43:06AM -0500, Joel Fernandes wrote:
> On Thu, Feb 28, 2019 at 11:17:51AM +0900, Masahiro Yamada wrote:
> > Hi Joel,
> >
> >
> > On Thu, Feb 28, 2019 at 4:40 AM Joel Fernandes (Google)
> > wrote:
> > >
> > > Introduce in-kernel headers and other artifacts which are mad
On Thu, Feb 28, 2019 at 05:04:59PM +0100, Dietmar Eggemann wrote:
[...] ^
> kernel/kheaders_data.h:1:1: note: in expansion of macro ‘KH_MAGIC_END’
> KH_MAGIC_END;
> ^~~~
> kernel/kheaders.c: In function ‘ikheaders_read_current’:
> kernel/kheaders.c:38:12: error: ‘kern
For ipcmni_extend mode, the sequence number space is only 7 bits. So
the chance of id reuse is relatively high compared with the non-extended
mode.
To alleviate this id reuse problem, the id allocation will be done
cyclically to cycle through all the 24-bit id space before wrapping
around when in
The mixing in of a sequence number into the IPC IDs is probably to
avoid ID reuse in userspace as much as possible. With ipcmni_extend
mode, the number of usable sequence numbers is greatly reduced leading
to higher chance of ID reuse.
To address this issue, we need to conserve the sequence number
The maximum number of unique System V IPC identifiers was limited to
32k. That limit should be big enough for most use cases.
However, there are some users out there requesting for more, especially
those that are migrating from Solaris which uses 24 bits for unique
identifiers. To satisfy the nee
v11->v12:
- As suggested by Matthew, change patch 2 to increment sequence number
when there is a wrap around in generated ID instead of after a
ID deletion.
v10->v11:
- Remove the sysctl parameter. Now delete mode is the only way the
sequence number is updated. The only choice users had
Quoting Paul Cercueil (2019-02-22 17:17:58)
> Bump.
>
> What should I do here?
>
I thought I replied to the list but maybe it got rejected because my MUA
is currently failing hard at sending 8-bit mails without
using quoted printable. Let me remove all non-ascii characters from this
mail!
If so
On 2/28/19 5:48 PM, Qais Yousef wrote:
On 02/28/19 17:04, Dietmar Eggemann wrote:
Hi Joel,
On 2/28/19 3:47 PM, Joel Fernandes wrote:
On Thu, Feb 28, 2019 at 01:53:43PM +, Qais Yousef wrote:
Hi Joel
On 02/27/19 14:37, Joel Fernandes (Google) wrote:
[...]
The reason for me to stay on v
On 28/02/2019 18:21, Catalin Marinas wrote:
On Thu, Feb 28, 2019 at 06:14:34PM +, Suzuki K Poulose wrote:
On 27/02/2019 01:05, Jeremy Linton wrote:
There are various reasons, including bencmarking, to disable spectrev2
mitigation on a machine. Provide a command-line to do so.
Signed-off
On Thu, Feb 28, 2019 at 06:14:34PM +, Suzuki K Poulose wrote:
> On 27/02/2019 01:05, Jeremy Linton wrote:
> > There are various reasons, including bencmarking, to disable spectrev2
> > mitigation on a machine. Provide a command-line to do so.
> >
> > Signed-off-by: Jeremy Linton
> > Cc: Jonat
Hi Jeremy
On 27/02/2019 01:05, Jeremy Linton wrote:
There are various reasons, including bencmarking, to disable spectrev2
mitigation on a machine. Provide a command-line to do so.
Signed-off-by: Jeremy Linton
Cc: Jonathan Corbet
Cc: linux-doc@vger.kernel.org
diff --git a/arch/arm64/kerne
On Thu, Feb 28, 2019 at 10:59:19AM -0500, Len Brown wrote:
> The SDM is like software -- usually (but not always) you are better
> off with the latest version:-)
If only it existed as a .tex file in a git repo. It has been very useful
to have older versions around a number of times.
Hi Paul,
On Thu, Feb 28, 2019 at 5:51 PM Paul E. McKenney wrote:
> On Thu, Feb 28, 2019 at 11:57:31AM +0100, Geert Uytterhoeven wrote:
> > Since the removal of FS_RECLAIM annotations, lockdep states contain six
> > characters, not four.
>
> Does the above want to instead say "four characters, not
On Thu, Feb 28, 2019 at 11:59:32AM +0100, Geert Uytterhoeven wrote:
> Suspicious RCU usage messages are reported as warnings.
>
> Fixes: a5dd63efda3d07b5 ("lockdep: Use "WARNING" tag on lockdep splats")
> Signed-off-by: Geert Uytterhoeven
Reviewed-by: Paul E. McKenney
> ---
> And before that,
On Thu, Feb 28, 2019 at 11:57:31AM +0100, Geert Uytterhoeven wrote:
> Since the removal of FS_RECLAIM annotations, lockdep states contain six
> characters, not four.
Does the above want to instead say "four characters, not six"?
Thanx, Paul
On 02/28/19 17:04, Dietmar Eggemann wrote:
> Hi Joel,
>
> On 2/28/19 3:47 PM, Joel Fernandes wrote:
> > On Thu, Feb 28, 2019 at 01:53:43PM +, Qais Yousef wrote:
> > > Hi Joel
> > >
> > > On 02/27/19 14:37, Joel Fernandes (Google) wrote:
>
> [...]
>
> > Ah good catch, I made this change for
On 02/28/19 17:04, Dietmar Eggemann wrote:
> Hi Joel,
>
> On 2/28/19 3:47 PM, Joel Fernandes wrote:
> > On Thu, Feb 28, 2019 at 01:53:43PM +, Qais Yousef wrote:
> > > Hi Joel
> > >
> > > On 02/27/19 14:37, Joel Fernandes (Google) wrote:
>
> [...]
>
> > Ah good catch, I made this change for
On Thu, 28 Feb 2019 16:45:13 +0100
Greg KH wrote:
> On Thu, Feb 28, 2019 at 10:37:41AM -0500, Joel Fernandes wrote:
> > In any case, it is not practical to provide headers for every kernel
> > version on
> > the system image and maintain them, it will take up too much space and has
> > to
> > b
Hi Joel,
On 2/28/19 3:47 PM, Joel Fernandes wrote:
On Thu, Feb 28, 2019 at 01:53:43PM +, Qais Yousef wrote:
Hi Joel
On 02/27/19 14:37, Joel Fernandes (Google) wrote:
[...]
Ah good catch, I made this change for "file_list=${@:2}" in my tree but
forgot to push it. Below is the updated pa
On Thu, Feb 28, 2019 at 7:45 AM Greg KH wrote:
>
> On Thu, Feb 28, 2019 at 10:37:41AM -0500, Joel Fernandes wrote:
> > In any case, it is not practical to provide headers for every kernel
> > version on
> > the system image and maintain them, it will take up too much space and has
> > to
> > be
On Tue, Feb 26, 2019 at 8:54 AM Peter Zijlstra wrote:
> > > It would've been nice to have the CPUID instruction 1F leaf reference
> > > 3B-3.9 in the SDM, and maybe mention this here too.
> >
> > I didn't mention SDM sections because they change -- leaving stale
> > pointers in our commit message
On Thu, Feb 28, 2019 at 10:37:41AM -0500, Joel Fernandes wrote:
> In any case, it is not practical to provide headers for every kernel version
> on
> the system image and maintain them, it will take up too much space and has to
> be periodically packaged. Not to mention that there will be kernel v
On Tue, Feb 26, 2019 at 2:46 PM Dave Hansen wrote:
>
> On 2/25/19 10:20 PM, Len Brown wrote:
> > -/* leaf 0xb sub-leaf types */
> > +/* extended topology sub-leaf types */
> > #define INVALID_TYPE 0
> > #define SMT_TYPE 1
> > #define CORE_TYPE2
> > +#define DIE_TYPE 5
>
> Looking in
On Thu, Feb 28, 2019 at 04:30:26PM +0100, Greg KH wrote:
> On Thu, Feb 28, 2019 at 10:00:54AM -0500, Joel Fernandes wrote:
> > > Hmm, isn't it easier to add kernel-headers package on Android?
> >
> > I have already been down that road. In the Android ecosystem, the Android
> > teams only provide a
On Thu, Feb 28, 2019 at 10:00:54AM -0500, Joel Fernandes wrote:
> > Hmm, isn't it easier to add kernel-headers package on Android?
>
> I have already been down that road. In the Android ecosystem, the Android
> teams only provide a "userspace system image" which goes on the system
> partition of t
On Thu, Feb 28, 2019 at 05:34:44PM +0900, Masami Hiramatsu wrote:
> Hi Joel,
>
> On Wed, 27 Feb 2019 14:37:47 -0500
> "Joel Fernandes (Google)" wrote:
>
> > Introduce in-kernel headers and other artifacts which are made available
> > as an archive through proc (/proc/kheaders.tar.xz file). This
On Thu, Feb 28, 2019 at 01:53:43PM +, Qais Yousef wrote:
> Hi Joel
>
> On 02/27/19 14:37, Joel Fernandes (Google) wrote:
> > Introduce in-kernel headers and other artifacts which are made available
> > as an archive through proc (/proc/kheaders.tar.xz file). This archive makes
> > it possible
On Thu, Feb 28, 2019 at 11:17:51AM +0900, Masahiro Yamada wrote:
> Hi Joel,
>
>
> On Thu, Feb 28, 2019 at 4:40 AM Joel Fernandes (Google)
> wrote:
> >
> > Introduce in-kernel headers and other artifacts which are made available
> > as an archive through proc (/proc/kheaders.tar.xz file). This ar
Hi Joel
On 02/27/19 14:37, Joel Fernandes (Google) wrote:
> Introduce in-kernel headers and other artifacts which are made available
> as an archive through proc (/proc/kheaders.tar.xz file). This archive makes
> it possible to build kernel modules, run eBPF programs, and other
> tracing programs
Suspicious RCU usage messages are reported as warnings.
Fixes: a5dd63efda3d07b5 ("lockdep: Use "WARNING" tag on lockdep splats")
Signed-off-by: Geert Uytterhoeven
---
And before that, they were printed as errors, which was also never
reflected in the documentation...
---
Documentation/RCU/lockde
Since the removal of FS_RECLAIM annotations, lockdep states contain six
characters, not four.
Fixes: e5684bbfc3f03480 ("Documentation/locking/lockdep: Update info about
states")
Fixes: d92a8cfcb37ecd13 ("locking/lockdep: Rework FS_RECLAIM annotation")
Signed-off-by: Geert Uytterhoeven
---
Docum
Hi Joel,
On Wed, 27 Feb 2019 14:37:47 -0500
"Joel Fernandes (Google)" wrote:
> Introduce in-kernel headers and other artifacts which are made available
> as an archive through proc (/proc/kheaders.tar.xz file). This archive makes
> it possible to build kernel modules, run eBPF programs, and othe
38 matches
Mail list logo
