On Wed, 5 Jul 2017 22:08:13 +0530
"Gautham R. Shenoy" wrote:
> From: "Gautham R. Shenoy"
>
> In the current idle initialization code, if there are failures in
> pnv_probe_idle_states, then no platform idle state is
> enabled. However, since the error is not propagated to the top-level
>
On Thu, 6 Jul 2017, Roman Gushchin wrote:
> +#define PGALLOC_EVENTS_SIZE (MAX_NR_ZONES * MAX_ORDER)
> +#define PGALLOC_EVENTS_CUT_SIZE (MAX_NR_ZONES * (MAX_ORDER - 1))
> +#define PGALLOC_FIRST_ZONE (PGALLOC_NORMAL - ZONE_NORMAL)
You are significantly increasing the per cpu counters (ZONES *
On Thu, Jul 06, 2017 at 04:48:40PM +0200, Christoph Hellwig wrote:
> Just did the whole batch (patch below), but it seems like using a
> __bitwise type in SYSCALL_DEFINE* will always give warnings like:
>
> fs/read_write.c:1095:1: warning: cast to restricted __kernel_rwf_t
>
> which I'm not
Michel Dänzer writes:
> Subtle breakage here: vblwait->request.sequence must still get updated
> for _DRM_VBLANK_RELATIVE, in case we're interrupted by a signal.
Thanks for finding this.
I think it might be better to just not modify the request.type field
instead, so that on re-entry it gets
Quoting Jeff Layton (jlay...@kernel.org):
> From: Jeff Layton
>
> The init_once routine memsets the whole object to 0, and then
> explicitly sets some of the fields to 0 again. Just remove the explicit
> initializations.
>
> Signed-off-by: Jeff Layton
Reviewed-by: Serge Hallyn
> ---
>
From: Colin Ian King
When us->extra is null the driver is not initialized, however, a
later call to osd200_scsi_to_ata is made that dereferences
us->extra, causing a null pointer dereference. The code
currently detects and reports that the driver is not initialized;
add a return to avoid the
On Thu, Jul 06, 2017 at 04:03:30PM +0100, Al Viro wrote:
> #define __SC_CAST(t, a) (__force t) a
>
> in syscalls.h
Hmm.
>
> > index a2d4a8ac94ca..a04adbc70ddf 100644
> > --- a/include/uapi/linux/aio_abi.h
> > +++ b/include/uapi/linux/aio_abi.h
> > @@ -28,6 +28,7 @@
> > #define
On Wed, 5 Jul 2017 22:08:14 +0530
"Gautham R. Shenoy" wrote:
> From: "Gautham R. Shenoy"
>
> In this patch we define a new function named pnv_power8_idle_init().
>
> We move the following code from pnv_init_idle_states() into this newly
> defined function.
>a) That patches out
On Thu, Jul 06, 2017 at 04:03:30PM +0100, Al Viro wrote:
> On Thu, Jul 06, 2017 at 04:48:40PM +0200, Christoph Hellwig wrote:
>
> > Just did the whole batch (patch below), but it seems like using a
> > __bitwise type in SYSCALL_DEFINE* will always give warnings like:
> >
> >
Michel Dänzer writes:
> BTW, this got me thinking that we should probably treat
> _DRM_VBLANK_NEXTONMISS the same way, i.e. clear the flag after updating
> vblwait->request.sequence. Otherwise there could theoretically (though
> unlikely) be an infinite loop:
I was thinking that we should just
On 06/07/2017 at 13:25:09 +, Miodrag Dinic wrote:
> > > +static int goldfish_rtc_read_time(struct device *dev, struct rtc_time
> > > *tm)
> > > +{
> > > + u64 time;
> > > + u64 time_low;
> > > + u64 time_high;
> > > + u64 time_high_prev;
> > > +
> > > + struct goldfish_rtc
On Wed, 5 Jul 2017 22:08:15 +0530
"Gautham R. Shenoy" wrote:
> From: "Gautham R. Shenoy"
>
> On POWER9 DD1, in order to get around a hardware issue, we store in
> every CPU thread's paca the paca pointers of all its siblings.
>
> Move this code into pnv_alloc_idle_core_states() soon after
On Tue, Jul 04, 2017 at 03:25:40PM +0200, Johan Hovold wrote:
> Add two missing include directives to two header files to avoid
> compile breakage when the required symbols have not already been
> defined.
>
> The missing SCU include broke compilation of the (not-yet-merged)
> suspend support for
On Thu, Jul 06, 2017 at 02:12:24PM +, David Laight wrote:
> From: Paul E. McKenney
> > Sent: 06 July 2017 00:30
> > There is no agreed-upon definition of spin_unlock_wait()'s semantics,
> > and it appears that all callers could do just as well with a lock/unlock
> > pair. This series
NAK. Don't overload xattrs with magic behavior just to avoid the need
to do proper syscalls or ioctls. This makes them harder to discover,
audit and security fix.
On Thu, Jul 06, 2017 at 03:50:27PM +0100, David Howells wrote:
> Add xattrs to allow the user to get/set metadata in lieu of having
On 7/6/2017 9:33 AM, Greg KH wrote:
On Thu, Jul 06, 2017 at 09:28:06AM -0500, Babu Moger wrote:
On 7/6/2017 3:24 AM, Max Filippov wrote:
Hi Babu,
On Tue, Jul 4, 2017 at 10:19 AM, Babu Moger wrote:
Max, Do you have any concerns about xtensa?
no, not ATM. I still haven't got a chance to
On Thu, Jul 6, 2017 at 5:45 AM, Eric W. Biederman wrote:
>
> How this is handled elsewhere in the code is to put the new values in
> bprm. Putting new rlimits in bprm and changing them in flush_old_exec
> or or setup_new_exec seems very sensible. It also allows for them to be
> accessed before
On 04/07/2017 at 13:59, Quentin Schulz wrote:
> This allows gclk to determine audio_pll rate and set the parent rate
> accordingly.
>
> However, there are multiple children clocks that could technically
> change the rate of audio_pll (via gck). With the rate locking, the first
> consumer to
On 06/07/2017 16:48, Peter Zijlstra wrote:
> On Thu, Jul 06, 2017 at 03:46:59PM +0200, Laurent Dufour wrote:
>> On 05/07/2017 20:50, Peter Zijlstra wrote:
>>> On Fri, Jun 16, 2017 at 07:52:33PM +0200, Laurent Dufour wrote:
@@ -2294,8 +2295,19 @@ static bool pte_map_lock(struct vm_fault *vmf)
On Wed, 5 Jul 2017 22:08:16 +0530
"Gautham R. Shenoy" wrote:
> From: "Gautham R. Shenoy"
>
> Currently, we use the opal call opal_slw_set_reg() to inform the that
> the Sleep-Winkle Engine (SLW) to restore the contents of some of the
> Hypervisor state on wakeup from deep idle states that
On Thu, Jul 6, 2017 at 5:38 AM, Eric W. Biederman wrote:
> Kees Cook writes:
>
>> In an attempt to provide sensible rlimit defaults for setuid execs, this
>> inherits the namespace's init rlimits:
>>
>> $ ulimit -s
>> 8192
>> $ ulimit -s unlimited
>> $ /bin/sh -c 'ulimit -s'
>> unlimited
>> $
On Wed, Jul 05, 2017 at 09:49:36AM -0700, Palmer Dabbelt wrote:
> On Mon, 03 Jul 2017 16:06:39 PDT (-0700), james.ho...@imgtec.com wrote:
> > On Thu, Jun 29, 2017 at 02:42:38PM -0700, Palmer Dabbelt wrote:
> >> On Wed, 28 Jun 2017 15:42:37 PDT (-0700), james.ho...@imgtec.com wrote:
> >> > On Wed,
On Thu, Jul 06, 2017 at 09:55:03AM +0100, Will Deacon wrote:
> Agreed on the indirection; it feels like this is something that should be in
> the vDSO, which could use the cmpxchg instruction if it's available, or
> otherwise just uses plain loads and stores.
Even that seems like a lot of
Daniel Vetter writes:
> A few nits below, but looks good otherwise.
Thanks.
>> static struct drm_pending_vblank_event *create_vblank_event(
>> -struct drm_device *dev, uint64_t user_data)
>> +struct drm_device *dev, struct drm_crtc *crtc, uint64_t
>> user_data)
>
>
On Thu, Jun 29, 2017 at 02:39:11PM +0300, Claudiu Beznea wrote:
> Document "start-offset" binding that will be used by at24
> EEPROM driver.
Why do we need this property?
Seems like this should be handled by defining regions of the EEPROM that
you care about (or perhaps are reserved and don't
On Thu, Jul 06, 2017 at 08:34:27AM -0700, Christoph Hellwig wrote:
> On Thu, Jul 06, 2017 at 09:55:03AM +0100, Will Deacon wrote:
> > Agreed on the indirection; it feels like this is something that should be in
> > the vDSO, which could use the cmpxchg instruction if it's available, or
> >
On Thu, Jul 06, 2017 at 05:10:33PM +0200, Christoph Hellwig wrote:
> On Thu, Jul 06, 2017 at 04:03:30PM +0100, Al Viro wrote:
> > On Thu, Jul 06, 2017 at 04:48:40PM +0200, Christoph Hellwig wrote:
> >
> > > Just did the whole batch (patch below), but it seems like using a
> > > __bitwise type in
On Thu, Jul 06, 2017 at 03:46:34PM +0100, Roman Gushchin wrote:
> > The alloc counter updates are themselves a surprisingly heavy cost to
> > the allocation path and this makes it worse for a debugging case that is
> > relatively rare. I'm extremely reluctant for such a patch to be added
> > given
On Thu, 6 Jul 2017, Colin King wrote:
> From: Colin Ian King
>
> When us->extra is null the driver is not initialized, however, a
> later call to osd200_scsi_to_ata is made that dereferences
> us->extra, causing a null pointer dereference. The code
> currently detects and reports that the
On Thu, Jul 6, 2017 at 6:43 AM, Christoph Lameter wrote:
> On Wed, 5 Jul 2017, Kees Cook wrote:
>
>> @@ -3536,6 +3565,9 @@ static int kmem_cache_open(struct kmem_cache *s,
>> unsigned long flags)
>> {
>> s->flags = kmem_cache_flags(s->size, flags, s->name, s->ctor);
>> s->reserved =
On 07/06/2017 06:44 AM, Serge E. Hallyn wrote:
> Quoting Geert Uytterhoeven (ge...@linux-m68k.org):
>> with W=2:
>>
>> security/apparmor/policy_unpack.c: In function ‘unpack_trans_table’:
>> security/apparmor/policy_unpack.c:469: warning: declaration of ‘pos’
>> shadows a previous local
On Thu, Jul 06, 2017 at 04:46:02PM +0100, Al Viro wrote:
> That - on #work.read_write, as in vfs.git at the moment...
... and for COMPAT_SYSCALL you need
#define __SC_DELOUSE(t,v) ((__force t)(unsigned long)(v))
in linux/compat.h
On Thu, Jul 06, 2017 at 10:54:24AM -0400, Debabrata Banerjee wrote:
> On Thu, Jul 6, 2017 at 9:19 AM, Mel Gorman
> wrote:
>
> > The alloc counter updates are themselves a surprisingly heavy cost to
> > the allocation path and this makes it worse for a debugging case that is
> > relatively rare.
On Thu, Jul 06, 2017 at 10:28:03AM -0500, Babu Moger wrote:
>
> On 7/6/2017 9:33 AM, Greg KH wrote:
> > On Thu, Jul 06, 2017 at 09:28:06AM -0500, Babu Moger wrote:
> > > On 7/6/2017 3:24 AM, Max Filippov wrote:
> > > > Hi Babu,
> > > >
> > > > On Tue, Jul 4, 2017 at 10:19 AM, Babu Moger
> > >
This patch adds I2C1 support for STM32F746 SoC.
Signed-off-by: M'boumba Cedric Madianga
Signed-off-by: Pierre-Yves MORDRET
---
Version history:
v3:
* None
v2:
* Update I2C SoC device tree with latest Linux version
---
---
arch/arm/boot/dts/stm32f746.dtsi | 22
This patch adds the documentation of device tree bindings for STM32F7 I2C
Signed-off-by: M'boumba Cedric Madianga
Signed-off-by: Pierre-Yves MORDRET
---
Version history:
v3:
* None
v2:
* Remove i2c-timing binding in order to use generic bindings SCL
Rising and
This patch uses a more generic definition of speed enum for i2c-stm32f4
driver.
Signed-off-by: M'boumba Cedric Madianga
Signed-off-by: Pierre-Yves MORDRET
Reviewed-by: Ludovic BARRE
---
Version history:
v3:
v2:
* None
---
---
drivers/i2c/busses/i2c-stm32.h | 20
This patchset adds support for the I2C controller embedded in STM32F7xx SoC.
It enables I2C transfer in interrupt mode with Standard-mode, Fast-mode and
Fast-mode+ bus speed.
---
Version history:
v3:
* Move stm32f7_i2c_match above stm32f7_i2c_driver
* of_device_get_match_data
On 7/6/2017 10:51 AM, Greg KH wrote:
On Thu, Jul 06, 2017 at 10:28:03AM -0500, Babu Moger wrote:
On 7/6/2017 9:33 AM, Greg KH wrote:
On Thu, Jul 06, 2017 at 09:28:06AM -0500, Babu Moger wrote:
On 7/6/2017 3:24 AM, Max Filippov wrote:
Hi Babu,
On Tue, Jul 4, 2017 at 10:19 AM, Babu Moger
On Thu, 6 Jul 2017, Kees Cook wrote:
> On Thu, Jul 6, 2017 at 6:43 AM, Christoph Lameter wrote:
> > On Wed, 5 Jul 2017, Kees Cook wrote:
> >
> >> @@ -3536,6 +3565,9 @@ static int kmem_cache_open(struct kmem_cache *s,
> >> unsigned long flags)
> >> {
> >> s->flags =
acpi_device_id are not supposed to change at runtime. All functions
working with acpi_device_id provided by work with
const acpi_device_id. So mark the non-const structs as const.
File size before:
textdata bss dec hex filename
53471920 2472911c7b
On Wed, 5 Jul 2017 09:58:57 +0100
Juri Lelli wrote:
> Hi,
>
> v1 of the RFC set implementing frequency/cpu invariance and OPP selection for
It would be nice if you specify what "OPP" stands for. A quick google
search shows "Other Peoples Privates", which isn't the type of
selection I would be
This patch adds initial support for the STM32F7 I2C controller.
Signed-off-by: M'boumba Cedric Madianga
Signed-off-by: Pierre-Yves MORDRET
---
Version history:
v3:
* Move stm32f7_i2c_match above stm32f7_i2c_driver
* of_device_get_match_data instead of of_match_device
This patch adds I2C1 support for STM32F746 eval board
Signed-off-by: M'boumba Cedric Madianga
Signed-off-by: Pierre-Yves MORDRET
---
Version history:
v3:
* None
v2:
* Add SCL Rising/Falling time for eval board
---
---
arch/arm/boot/dts/stm32746g-eval.dts | 8
On 07/03/2017 09:56 PM, Ethan Zhao wrote:
James,
On Tue, Jul 4, 2017 at 2:17 AM, james puthukattukaran
wrote:
Ethan -
On 7/2/2017 9:55 PM, Ethan Zhao wrote:
James,
On Wed, Jun 28, 2017 at 5:42 AM, James Puthukattukaran
wrote:
From: James Puthukattukaran
The IDT switch incorrectly
Add API functions for registering and removing a notifier for FPGA
manager register/unregister events. Notify when a new FPGA manager
has been registered or when an existing manager is being removed.
This will help configuration interface drivers to get the notion
of low-level FPGA managers
On Wed, Jul 05, 2017 at 11:35:52AM +0800, changbin...@intel.com wrote:
> From: Changbin Du
>
> If we always insert 'overhead' and 'overhead_children' as sort keys,
> this make it impossible to sort as overhead (which displayed as Self)
> first.Ths will be a problem if the data is collected with
On Thu, Jul 06, 2017 at 02:12:24PM +, David Laight wrote:
> From: Paul E. McKenney
> > Sent: 06 July 2017 00:30
> > There is no agreed-upon definition of spin_unlock_wait()'s semantics,
> > and it appears that all callers could do just as well with a lock/unlock
> > pair. This series
From: James Puthukattukaran
The IDT switch incorrectly flags an ACS source violation on a read config
request to an end point device on the completion (IDT 89H32H8G3-YC,
errata #36) even though the PCI Express spec states that completions are
never affected by ACS source violation (PCI Spec
acpi_device_id are not supposed to change at runtime. All functions
working with acpi_device_id provided by work with
const acpi_device_id. So mark the non-const structs as const.
File size before:
textdata bss dec hex filename
124663120 8 155943cea
On 06/07/17 11:57, Steven Rostedt wrote:
> On Wed, 5 Jul 2017 09:58:57 +0100
> Juri Lelli wrote:
>
> > Hi,
> >
> > v1 of the RFC set implementing frequency/cpu invariance and OPP selection
> > for
>
> It would be nice if you specify what "OPP" stands for. A quick google
> search shows "Other
On 06/07/2017 at 17:29:22 +0200, Nicolas Ferre wrote:
> > + /*
> > +* The audio_pll rate can be modified, unlike the five others clocks
> > +* that should never be altered.
> > +* The audio_pll can technically be used by multiple consumers. However,
> > +* with the rate locking,
On Thu, Jul 06, 2017 at 08:21:10AM -0700, Paul E. McKenney wrote:
> And yes, there are architecture-specific optimizations for an
> empty spin_lock()/spin_unlock() critical section, and the current
> arch_spin_unlock_wait() implementations show some of these optimizations.
> But I expect that
On Thu, Jul 6, 2017 at 11:51 AM, Mel Gorman wrote:
>
> These counters do not actually help you solve that particular problem.
> Knowing how many allocations happened since the system booted doesn't tell
> you much about how many failed or why they failed. You don't even know
> what frequency they
On Thu, Jul 06, 2017 at 05:29:26PM +0200, Laurent Dufour wrote:
> Based on the benchmarks I run, it doesn't fail so much often, but I was
> thinking about adding some counters here. The system is accounting for
> major page faults and minor ones, respectively current->maj_flt and
>
Christoph Hellwig wrote:
> NAK. Don't overload xattrs with magic behavior just to avoid the need
> to do proper syscalls or ioctls.
How? This has to work on non-files, files you can't open and mountpoints.
You can't do an ioctl() on a file opened O_PATH:
if (unlikely(f->f_flags &
acpi_device_id are not supposed to change at runtime. All functions
working with acpi_device_id provided by work with
const acpi_device_id. So mark the non-const structs as const.
File size before:
textdata bss dec hex filename
238048448 0 322527dfc
On Thu, Jul 06, 2017 at 11:57:15AM -0400, Steven Rostedt wrote:
> On Wed, 5 Jul 2017 09:58:57 +0100
> Juri Lelli wrote:
>
> > Hi,
> >
> > v1 of the RFC set implementing frequency/cpu invariance and OPP selection
> > for
>
> It would be nice if you specify what "OPP" stands for. A quick
On Thu, 2017-07-06 at 10:55 -0500, Christoph Lameter wrote:
> On Thu, 6 Jul 2017, Kees Cook wrote:
>
> > On Thu, Jul 6, 2017 at 6:43 AM, Christoph Lameter
> > wrote:
> > > On Wed, 5 Jul 2017, Kees Cook wrote:
> > >
> > > > @@ -3536,6 +3565,9 @@ static int kmem_cache_open(struct
> > > >
The mremap system call has the ability to 'mirror' parts of an existing
mapping. To do so, it creates a new mapping that maps the same pages as
the original mapping, just at a different virtual address. This
functionality has existed since at least the 2.6 kernel [1]. A comment
was added to the
The mremap system call has the ability to 'mirror' parts of an existing
mapping. To do so, it creates a new mapping that maps the same pages as
the original mapping, just at a different virtual address. This
functionality has existed since at least the 2.6 kernel.
This patch simply adds a new
On Thu, Jul 06, 2017 at 06:05:55PM +0200, Peter Zijlstra wrote:
> On Thu, Jul 06, 2017 at 02:12:24PM +, David Laight wrote:
> > From: Paul E. McKenney
[ . . . ]
> Now on the one hand I feel like Oleg that it would be a shame to loose
> the optimization, OTOH this thing is really really
acpi_device_id are not supposed to change at runtime. All functions
working with acpi_device_id provided by work with
const acpi_device_id. So mark the non-const structs as const.
File size before:
textdata bss dec hex filename
102971888 0 121852f99
Hi Linus,
The following changes since commit 63f700aab4c11d46626de3cd051dae56cf7e9056:
Merge tag 'xtensa-20170612' of
git://github.com/jcmvbkbc/linux-xtensa (2017-06-13 15:09:10 +0900)
are available in the git repository at:
From: Jeff Layton
The IMA assessment code tries to use the i_version counter to detect
when changes to a file have occurred. Many filesystems don't increment
it properly (or at all) so detecting changes with that is not always
reliable.
That check should really be gated on IS_I_VERSION. When
On Thu, Jul 06, 2017 at 06:10:47PM +0200, Peter Zijlstra wrote:
> On Thu, Jul 06, 2017 at 08:21:10AM -0700, Paul E. McKenney wrote:
> > And yes, there are architecture-specific optimizations for an
> > empty spin_lock()/spin_unlock() critical section, and the current
> > arch_spin_unlock_wait()
Em Tue, Jun 20, 2017 at 08:22:09PM +0800, Jin Yao escreveu:
> Macro fusion merges two instructions to a single micro-op. Intel
> core platform performs this hardware optimization under limited
> circumstances.
>
> For example, CMP + JCC can be "fused" and executed /retired
> together. While with
Daniel Vetter writes:
> I very much like this since the old ioctl really is a rather bad horror
> show. And since it's tied in with ums drivers everything is
> complicated.
Thanks for your kind words.
> I started a discussion a while back whether these should be restricted to
> DRM_MASTER
On Wed, Jul 05, 2017 at 04:46:26PM +0300, Igor Stoppa wrote:
> The MMU available in many systems running Linux can often provide R/O
> protection to the memory pages it handles.
>
> However, the MMU-based protection works efficiently only when said pages
> contain exclusively data that will not
Ville Syrjälä writes:
> Maybe, or maybe we want to turn the interrupt on in that case? That's
> what the old ioctl does.
That's what I suggested in my reply to Daniel's review. Even if we add
the accurate function, we'll still need the interrupt-enable case as a
fallback for drivers which don't
acpi_device_id are not supposed to change at runtime. All functions
working with acpi_device_id provided by work with
const acpi_device_id. So mark the non-const structs as const.
File size before:
textdata bss dec hex filename
147711880 0 16651410b
On Thu, Jun 29, 2017 at 12:41:07PM -0700, Nick Terrell wrote:
> Add zstd compression and decompression support to BtrFS. zstd at its
> fastest level compresses almost as well as zlib, while offering much
> faster compression and decompression, approaching lzo speeds.
Got a reproducible crash on
On Wed, Jul 5, 2017 at 9:32 PM, Kees Cook wrote:
> In an attempt to provide sensible rlimit defaults for setuid execs, this
> inherits the namespace's init rlimits:
Yeah, so I have to admit to hating this patch.
As already mentioned by others, it's not only not clear that we want
to do this on
We have seen some generic code use config parameter CONFIG_CPU_BIG_ENDIAN
to decide the endianness.
Here are the few examples.
include/asm-generic/qrwlock.h
drivers/of/base.c
drivers/of/fdt.c
drivers/tty/serial/earlycon.c
drivers/tty/serial/serial_core.c
Display warning if CPU_BIG_ENDIAN is not
Resending the series per Greg KH's request.
Found this problem while enabling queued rwlock on SPARC.
The parameter CONFIG_CPU_BIG_ENDIAN is used to clear the
specific byte in qrwlock structure. Without this parameter,
we clear the wrong byte.
Here is the code in include/asm-generic/qrwlock.h
While working on enabling queued rwlock on SPARC, found
this following code in include/asm-generic/qrwlock.h
which uses CONFIG_CPU_BIG_ENDIAN to clear a byte.
static inline u8 *__qrwlock_write_byte(struct qrwlock *lock)
{
return (u8 *)lock + 3 * IS_BUILTIN(CONFIG_CPU_BIG_ENDIAN);
}
microblaze architectures can be configured for either little or
big endian formats. Add a choice option for the user to select the
correct endian format(default to big endian).
Also update the Makefile so toolchain can compile for the format
it is configured for.
Signed-off-by: Babu Moger
Hello,
On Thursday, 6 July 2017 05:03:59 PDT Thomas Gleixner wrote:
> On Thu, 6 Jul 2017, jrj...@gmail.com wrote:
>
> CC+ MIPS folks. There is a reason WHY I added them to my previous reply.
Thanks Thomas.
> > From: Jun-Ru Chang
> >
> > Commit b87281e7f205 ("irqchip/mips-gic: Remove device
acpi_device_id are not supposed to change at runtime. All functions
working with acpi_device_id provided by work with
const acpi_device_id. So mark the non-const structs as const.
File size before:
textdata bss dec hex filename
207293264 0 239935db9
Hi gengdongjiu,
On 05/07/17 09:14, gengdongjiu wrote:
> On 2017/7/4 18:14, James Morse wrote:
>> Can you give us a specific example of an error you are trying to handle?
> For example:
> guest OS user space accesses device type memory, but happen SError. because
> the
> SError is asynchronous
acpi_device_id are not supposed to change at runtime. All functions
working with acpi_device_id provided by work with
const acpi_device_id. So mark the non-const structs as const.
File size before:
textdata bss dec hex filename
151482640 8 177964584
On Thu, Jul 06, 2017 at 09:24:12AM -0700, Paul E. McKenney wrote:
> On Thu, Jul 06, 2017 at 06:10:47PM +0200, Peter Zijlstra wrote:
> > On Thu, Jul 06, 2017 at 08:21:10AM -0700, Paul E. McKenney wrote:
> > > And yes, there are architecture-specific optimizations for an
> > > empty
El Sat, Jul 01, 2017 at 01:11:12PM +0100 Jonathan Cameron ha dit:
> On Thu, 29 Jun 2017 14:51:56 +0200
> Linus Walleij wrote:
>
> > On Tue, Jun 27, 2017 at 2:25 AM, Matthias Kaehlcke
> > wrote:
> >
> > > Don't inflate the kernel size with data that isn't used. The conditional
> > >
On Thu, Jul 06, 2017 at 12:12:47PM -0400, Debabrata Banerjee wrote:
> On Thu, Jul 6, 2017 at 11:51 AM, Mel Gorman
> wrote:
> >
> > These counters do not actually help you solve that particular problem.
> > Knowing how many allocations happened since the system booted doesn't tell
> > you much
acpi_device_id are not supposed to change at runtime. All functions
working with acpi_device_id provided by work with
const acpi_device_id. So mark the non-const structs as const.
File size before:
textdata bss dec hex filename
107541360 4 121182f56
On Thu, Jul 06, 2017 at 04:47:05PM +0100, Mel Gorman wrote:
> On Thu, Jul 06, 2017 at 03:46:34PM +0100, Roman Gushchin wrote:
> > > The alloc counter updates are themselves a surprisingly heavy cost to
> > > the allocation path and this makes it worse for a debugging case that is
> > > relatively
On 06/07/17 15:37, Jassi Brar wrote:
> On Thu, Jul 6, 2017 at 3:03 PM, Sudeep Holla wrote:
[...]
>>
>> I said it *may not be used*, currently it is used.
>>
> SCPI provides more than what SCMI currently does - dvfs, clock, sensor.
Not sure what you mean by that, but that's not true.
> I see
On Thu, 6 Jul 2017, Paul E. McKenney wrote:
> On Thu, Jul 06, 2017 at 06:10:47PM +0200, Peter Zijlstra wrote:
> > On Thu, Jul 06, 2017 at 08:21:10AM -0700, Paul E. McKenney wrote:
> > > And yes, there are architecture-specific optimizations for an
> > > empty spin_lock()/spin_unlock() critical
Got that at a hardened Gentoo Linux server with 4.12.0 (for the first time) at
a BTRFS logical volume occuping about 4/9 of a 5 TB volume group after an
uptime of about 2 days :
Had issues with processes accessing files at that volume now too.
Jul 6 15:33:53 mr-fox kernel: [158695.417132]
acpi_device_id are not supposed to change at runtime. All functions
working with acpi_device_id provided by work with
const acpi_device_id. So mark the non-const structs as const.
File size before:
textdata bss dec hex filename
2208 400 02608 a30
On Thu, Jul 6, 2017 at 9:34 AM, Linus Torvalds
wrote:
>
> (a) minimal: just use our existing default stack (and stack _only_)
> limit value for suid binaries that actually get extra permissions: {
> _STK_LIM, RLIM_INFINITY }.
>
> (c) perhaps encourage people to annotate their suid binaries with
On Thu, Jul 06, 2017 at 09:20:24AM -0700, Paul E. McKenney wrote:
> On Thu, Jul 06, 2017 at 06:05:55PM +0200, Peter Zijlstra wrote:
> > On Thu, Jul 06, 2017 at 02:12:24PM +, David Laight wrote:
> > > From: Paul E. McKenney
>
> [ . . . ]
>
> > Now on the one hand I feel like Oleg that it
On Thu, Jul 06, 2017 at 12:49:12PM -0400, Alan Stern wrote:
> On Thu, 6 Jul 2017, Paul E. McKenney wrote:
>
> > On Thu, Jul 06, 2017 at 06:10:47PM +0200, Peter Zijlstra wrote:
> > > On Thu, Jul 06, 2017 at 08:21:10AM -0700, Paul E. McKenney wrote:
> > > > And yes, there are architecture-specific
acpi_device_id are not supposed to change at runtime. All functions
working with acpi_device_id provided by work with
const acpi_device_id. So mark the non-const structs as const.
File size before:
textdata bss dec hex filename
1733 352 02085 825
On Thu, Jul 06, 2017 at 04:51:13PM +0100, Al Viro wrote:
> On Thu, Jul 06, 2017 at 04:46:02PM +0100, Al Viro wrote:
>
> > That - on #work.read_write, as in vfs.git at the moment...
>
> ... and for COMPAT_SYSCALL you need
> #define __SC_DELOUSE(t,v) ((__force t)(unsigned long)(v))
> in
On Wed, Jul 5, 2017 at 2:51 PM, Patrick Venture wrote:
> This driver can be used on the aspeed ast2400 with minor
> modifications.
>
> Tested: ast2400 on quanta-q71l
>
> Signed-off-by: Patrick Venture
> ---
> v3: added .data object to determine behavior difference between ast2400 and
>
On Thu, Jul 6, 2017 at 10:00 AM, Patrick Venture wrote:
> On Wed, Jul 5, 2017 at 2:51 PM, Patrick Venture wrote:
>> This driver can be used on the aspeed ast2400 with minor
>> modifications.
>>
>> Tested: ast2400 on quanta-q71l
>>
>> Signed-off-by: Patrick Venture
>> ---
>> v3: added .data
On Thu, Jul 06, 2017 at 06:41:34PM +0200, Peter Zijlstra wrote:
> On Thu, Jul 06, 2017 at 09:24:12AM -0700, Paul E. McKenney wrote:
> > On Thu, Jul 06, 2017 at 06:10:47PM +0200, Peter Zijlstra wrote:
> > > On Thu, Jul 06, 2017 at 08:21:10AM -0700, Paul E. McKenney wrote:
> > > > And yes, there are
This driver can be used on the aspeed ast2400 with minor
modifications.
Tested: ast2400 on quanta-q71l
Signed-off-by: Patrick Venture
---
v4: fix the 2400/2500 data as they were backwards.
v3: added .data object to determine behavior difference between ast2400 and
ast2500.
v2: added
On Fri, Jun 30, 2017 at 6:21 AM, Enric Balletbo i Serra
wrote:
> From: huang lin
>
> Add a pwm-delay-us property to specify the delay between setting an
> initial (non-zero) PWM value and enabling the backlight, and also the
> delay between disabling the backlight and setting PWM value to 0.
>
>
1401 - 1500 of 1854 matches
Mail list logo
