After applying this node the LSM303DLH sensor chip should probe
successfully once the driver support has also been applied.
Signed-off-by: Lee Jones
---
arch/arm/boot/dts/ste-snowball.dts | 8
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/ste-snowball.dts
b/arch/arm/b
> > So in the mean time are you happy with this "dummy" approach?
>
> No. "dummy" is reserved for a dummy device in case an i2c slave needs
> more than one address. The proper solution would be if
> i2c_sysfs_new_device() could recognize the of_device_ids.
Okay, thanks for clarifying.
--
Lee Jo
LSM303DLH is a Accelerometer Sensor
Cc: devicet...@vger.kernel.org
Signed-off-by: Lee Jones
---
.../devicetree/bindings/iio/accel/lsm303dlhc.txt| 21 +
1 file changed, 21 insertions(+)
create mode 100644 Documentation/devicetree/bindings/iio/accel/lsm303dlhc.txt
diff --
After applying this node the LSM303DLH sensor chip should probe
successfully once the driver support has also been applied.
Signed-off-by: Lee Jones
---
arch/arm/boot/dts/ste-snowball.dts | 8
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/ste-snowball.dts
b/arch/arm/b
> There already was an implicit division there, and
> sizeof(pebs_record_hsw) = 176, can it really optimize that constant
> division?
Yes it can (if nothing else then by converting it to * 1/x)
The only exception is with -Os, but if you want performance
you should not be using that anyways.
You
Hi Jonathan,
Hopefully I've covered all of your points in this new set.
This patch-set includes a few clean-ups surrounding error handling and
non-mandatory functionality along with regulator support and the addition
of a new pressure/temperature sensor (LPS001WP).
Everything has been tested wit
The power to some of the sensors are controlled by regulators. In most
cases these are 'always on', but if not they will fail to work until
the regulator is enabled using the relevant APIs. This patch allows for
the Vdd_IO power supply to be specified by either platform data or
Device Tree.
Signed
Gets rid of those unnecessary gotos.
Signed-off-by: Lee Jones
---
drivers/iio/common/st_sensors/st_sensors_core.c | 8 +++-
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/drivers/iio/common/st_sensors/st_sensors_core.c
b/drivers/iio/common/st_sensors/st_sensors_core.c
index c
>
> /*
>* Should not happen, we program the threshold at 1 and do not
>* set a reset value.
>*/
> - WARN_ONCE(n > x86_pmu.max_pebs_events,
> - "Unexpected number of pebs records %d\n", n);
> + WARN_ONCE(top - at > x86_pmu.max_pebs_events * x86_p
L3G4200D is a Gyroscope Sensor
Cc: devicet...@vger.kernel.org
Signed-off-by: Lee Jones
---
.../devicetree/bindings/iio/gyro/l3g4200d.txt | 21 +
1 file changed, 21 insertions(+)
create mode 100644 Documentation/devicetree/bindings/iio/gyro/l3g4200d.txt
diff --git a/Do
Turns out that they're actually not required and the driver probes just
fine without them. The ID is incorrect at the moment anyway. They actually
currently specify the stn8815.
Signed-off-by: Lee Jones
---
arch/arm/boot/dts/ste-dbx5x0.dtsi | 5 -
1 file changed, 5 deletions(-)
diff --git a
LSM303DLH is a Magnetometer Sensor
Cc: devicet...@vger.kernel.org
Signed-off-by: Lee Jones
---
.../bindings/iio/magnetometer/lsm303dlhc.txt| 21 +
1 file changed, 21 insertions(+)
create mode 100644
Documentation/devicetree/bindings/iio/magnetometer/lsm303dlhc.txt
Reduce the amount of those unnecessary goto calls, as in most cases
we can simply return immediately. We also only call for the IRQ number
once and use that value throughout.
Signed-off-by: Lee Jones
---
drivers/iio/gyro/st_gyro_core.c | 19 ++-
1 file changed, 10 insertions(+),
clears following warnings :
WARNING: Use include instead of
WARNING: Use include instead of
Signed-off-by: Avinash Kumar
---
drivers/net/phy/cicada.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/net/phy/cicada.c b/drivers/net/phy/cicada.c
index db472ff..
The power to some of the sensors are controlled by regulators. In most
cases these are 'always on', but if not they will fail to work until
the regulator is enabled using the relevant APIs. This patch allows for
the Vdd power supply to be specified by either platform data or Device
Tree.
Signed-of
This patch contains some pretty basic clean-ups in probe() pertaining to
the simplification of error handling and a couple of readability adaptions.
Signed-off-by: Lee Jones
---
drivers/iio/pressure/st_pressure_core.c | 28 +++-
1 file changed, 15 insertions(+), 13 deleti
Here we use existing practices to introduce support for another
pressure/temperature sensor, the LPS001WP.
Signed-off-by: Lee Jones
---
drivers/iio/pressure/st_pressure.h | 1 +
drivers/iio/pressure/st_pressure_core.c | 84 +
drivers/iio/pressure/st_pressure
Reduce the amount of those unnecessary goto calls, as in most cases
we can simply return immediately. We also only call for the IRQ number
once and use that value throughout.
Signed-off-by: Lee Jones
---
drivers/iio/magnetometer/st_magn_core.c | 19 ++-
1 file changed, 10 inserti
After applying this node the L3G4200D sensor chip should probe
successfully once the driver support has also been applied.
Signed-off-by: Lee Jones
---
arch/arm/boot/dts/ste-snowball.dts | 8
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/ste-snowball.dts
b/arch/arm/bo
These include; Pressure, Accelerometer, Magnetometer and Gyroscope Sensors
Signed-off-by: Lee Jones
---
arch/arm/configs/u8500_defconfig | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm/configs/u8500_defconfig b/arch/arm/configs/u8500_defconfig
index a0025dc..aaa6c0a 100644
---
LPS001WP is a Pressure and Temperature sensor.
Cc: devicet...@vger.kernel.org
Signed-off-by: Lee Jones
---
.../devicetree/bindings/iio/pressure/lps001wp.txt | 21 +
1 file changed, 21 insertions(+)
create mode 100644 Documentation/devicetree/bindings/iio/pressure/lps001wp.
After applying this node the LPS001WP sensor chip should probe
successfully once the driver support has also been applied.
Signed-off-by: Lee Jones
---
arch/arm/boot/dts/ste-snowball.dts | 10 ++
1 file changed, 10 insertions(+)
diff --git a/arch/arm/boot/dts/ste-snowball.dts
b/arch/ar
> All users of %n are calculating padding size when using seq_file, so
> instead use the new last_len member for discovering the length of the
> written strings.
Obviously, this comment needs to be updated, but once that is done,
Acked-by: George Spelvin .
I actually reviewed all the users and ch
Strip out all those unnecessary gotos and just return the error right away.
Aids to simplicity and reduces code.
Signed-off-by: Lee Jones
---
drivers/iio/common/st_sensors/st_sensors_core.c | 9 -
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/drivers/iio/common/st_sensor
On Monday 16 September 2013 13:43:50, Stephen Warren wrote:
> On 09/10/2013 06:52 PM, Javier Martinez Canillas wrote:
> > On 09/11/2013 12:34 AM, Stephen Warren wrote:
> >> On 09/10/2013 03:37 PM, Mark Brown wrote:
> >>> On Tue, Sep 10, 2013 at 01:53:47PM -0600, Stephen Warren wrote:
> Doesn't
Hi Ingo,
Do you have an estimate of the time it will take for this fix to hit
mainline, stable-3.10 and stable-3.11 ? Meanwhile, I'm marking 3.10 and
3.11 as broken for LTTng with a kernel version at compile-time, since
this kernel regression currently triggers hard system lockup when people
use L
Not all ST's sensors support data ready, so let's make the declaration
of one conditional.
Signed-off-by: Lee Jones
---
drivers/iio/common/st_sensors/st_sensors_core.c | 33 -
drivers/iio/pressure/st_pressure_core.c | 3 ++-
2 files changed, 24 insertions(+), 12
Reduce the amount of those unnecessary goto calls, as in most cases
we can simply return immediately. We also only call for the IRQ number
once and use that value throughout.
Signed-off-by: Lee Jones
---
drivers/iio/accel/st_accel_core.c | 19 ++-
1 file changed, 10 insertions(+)
> So in the mean time are you happy with this "dummy" approach?
No. "dummy" is reserved for a dummy device in case an i2c slave needs
more than one address. The proper solution would be if
i2c_sysfs_new_device() could recognize the of_device_ids.
signature.asc
Description: Digital signature
On Mon, Sep 16, 2013 at 01:50:46PM +0200, Laszlo Ersek wrote:
> On 09/16/13 12:59, Matt Fleming wrote:
> > On Fri, 13 Sep, at 02:38:12PM, jerry.hoem...@hp.com wrote:
> >> Matt,
> >>
> >> We have hit an issue on our new platform in development related to the
> >> call of efi_reserve_boot_services()
On Mon, Sep 16, 2013 at 8:17 AM, Thierry Reding
wrote:
> On Wed, Sep 11, 2013 at 09:41:49PM -0700, Olof Johansson wrote:
>> This removes two warnings where dma_addr_t variables were printed using
>> %x when built with CONFIG_ARM_LPAE=y, thus having 64-bit dma_addr_t:
>>
>> drivers/gpu/host1x/hw/
* Stephane Eranian wrote:
> Hi,
>
> Some updates on this problem.
> I have been running tests all week-end long on my HSW.
> I can reproduce the problem. What I know:
>
> - It is not linked with callchain
> - The extra entries are valid
> - The reset values are still zeroes
> - The problem doe
On Mon, 2013-09-16 at 08:25 -0700, Kees Cook wrote:
> On Mon, Sep 16, 2013 at 8:09 AM, Joe Perches wrote:
> > On Mon, 2013-09-16 at 07:59 -0700, Kees Cook wrote:
> >> Perhaps instead of seq->count, there should be an access function?
> >> seq_get_count(seq) or something?
> >
> > My thought was to
On Mon, 2013-09-16 at 08:46 -0700, Olof Johansson wrote:
> On Mon, Sep 16, 2013 at 8:17 AM, Thierry Reding
> wrote:
> > On Wed, Sep 11, 2013 at 09:41:49PM -0700, Olof Johansson wrote:
> >> This removes two warnings where dma_addr_t variables were printed using
> >> %x when built with CONFIG_ARM_LP
On Mon, Sep 16, 2013 at 05:16:20PM +0300, Gleb Natapov wrote:
> On Mon, Sep 16, 2013 at 02:03:33PM +0200, Andrew Jones wrote:
> > On Mon, Sep 16, 2013 at 11:47:10AM +0300, Gleb Natapov wrote:
> > > On Mon, Sep 16, 2013 at 10:28:20AM +0200, Andrew Jones wrote:
> > > > On Sun, Sep 15, 2013 at 12:08:3
On Mon, Sep 16, 2013 at 05:18:22PM +0200, Peter Zijlstra wrote:
> On Tue, Sep 10, 2013 at 10:31:54AM +0100, Mel Gorman wrote:
> > @@ -860,9 +908,14 @@ void task_numa_fault(int node, int pages, bool
> > migrated)
> > * If pages are properly placed (did not migrate) then scan slower.
> > *
> CC: "Johannes Weiner" , "Andrew Morton"
> , "David Rientjes" ,
> "KAMEZAWA Hiroyuki" , "KOSAKI Motohiro"
> , linux...@kvack.org,
> cgro...@vger.kernel.org, x...@kernel.org, linux-a...@vger.kernel.org,
> linux-kernel@vger.kernel.org
>On Mon 16-09-13 17:05:43, azurIt wrote:
>> > CC: "Johannes
> -Original Message-
> From: Dmitry Torokhov [mailto:dmitry.torok...@gmail.com]
> Sent: Monday, September 16, 2013 8:20 AM
> To: KY Srinivasan
> Cc: gre...@linuxfoundation.org; linux-kernel@vger.kernel.org;
> de...@linuxdriverproject.org; linux-in...@vger.kernel.org; vojt...@suse.cz;
> o.
On Mon, 16 Sep 2013, Wolfram Sang wrote:
>
> On Mon, Sep 16, 2013 at 02:51:18PM +0100, Mark Brown wrote:
> > On Mon, Sep 16, 2013 at 02:44:35PM +0200, Linus Walleij wrote:
> >
> > > I've tried to fix this for DT-only I2C devices
> > > and this very driver was the reason.
> >
> > > But a tiresom
Lee Jones wrote:
>On Sat, 14 Sep 2013, Jonathan Cameron wrote:
>
>> On 09/10/13 13:49, Lee Jones wrote:
>> > At the moment the number of channels specified is dictated by the
>first
>> > sensor supported by the driver. As we add support for more sensors
>this
>> > is likely to vary. Instead of u
On Wed, Sep 11, 2013 at 09:41:49PM -0700, Olof Johansson wrote:
> This removes two warnings where dma_addr_t variables were printed using
> %x when built with CONFIG_ARM_LPAE=y, thus having 64-bit dma_addr_t:
>
> drivers/gpu/host1x/hw/cdma_hw.c:57:3: warning: format '%x' expects argument
> of t
On Mon, Sep 16, 2013 at 02:51:18PM +0100, Mark Brown wrote:
> On Mon, Sep 16, 2013 at 02:44:35PM +0200, Linus Walleij wrote:
>
> > I've tried to fix this for DT-only I2C devices
> > and this very driver was the reason.
>
> > But a tiresome regression due to drivers relying on this
> > i2c_device
Hi K. Y.
On Sun, Sep 15, 2013 at 10:28:54PM -0700, K. Y. Srinivasan wrote:
> Add a new driver to support synthetic keyboard. On the next generation
> Hyper-V guest firmware, many legacy devices will not be emulated and this
> driver will be required.
>
> I would like to thank Vojtech Pavlik for
On 09/16/2013 10:47 AM, Fengguang Wu wrote:
> Greetings,
>
> I got the below dmesg and the first bad commit is
>
> commit 7a8010cd36273ff5f6fea5201ef9232f30cebbd9
> Author: Vlastimil Babka
> Date: Wed Sep 11 14:22:35 2013 -0700
>
> mm: munlock: manual pte walk in fast path instead of foll
On Mon 16-09-13 17:05:43, azurIt wrote:
> > CC: "Johannes Weiner" , "Andrew Morton"
> > , "David Rientjes" ,
> > "KAMEZAWA Hiroyuki" , "KOSAKI Motohiro"
> > , linux...@kvack.org,
> > cgro...@vger.kernel.org, x...@kernel.org, linux-a...@vger.kernel.org,
> > linux-kernel@vger.kernel.org
> >On Mo
On Mon, Sep 16, 2013 at 8:09 AM, Joe Perches wrote:
> On Mon, 2013-09-16 at 07:59 -0700, Kees Cook wrote:
>> Perhaps instead of seq->count, there should be an access function?
>> seq_get_count(seq) or something?
>
> My thought was to add a seq_last_len()
That would mean growing the size of the se
> CC: "Michal Hocko" , "Andrew Morton"
> , "David Rientjes" ,
> "KAMEZAWA Hiroyuki" , "KOSAKI Motohiro"
> , linux...@kvack.org,
> cgro...@vger.kernel.org, x...@kernel.org, linux-a...@vger.kernel.org,
> linux-kernel@vger.kernel.org
>On Mon, Sep 16, 2013 at 05:05:43PM +0200, azurIt wrote:
>> > C
On Sep 15, 2013, at 9:57 PM, Benjamin Herrenschmidt wrote:
> [resent to the right list this time around]
>
> Hi folks !
>
> So I don't have the bandwidth to follow closely what's going on, but I
> just today noticed the crackpot that went into 3.11 as part of commit:
>
> 9d8eab7af79cb4ce2de5de
On Mon, Sep 16, 2013 at 05:05:43PM +0200, azurIt wrote:
> > CC: "Johannes Weiner" , "Andrew Morton"
> > , "David Rientjes" ,
> > "KAMEZAWA Hiroyuki" , "KOSAKI Motohiro"
> > , linux...@kvack.org,
> > cgro...@vger.kernel.org, x...@kernel.org, linux-a...@vger.kernel.org,
> > linux-kernel@vger.ker
On Mon, Sep 16, 2013 at 05:41:18PM +0300, Gleb Natapov wrote:
> On Mon, Sep 16, 2013 at 01:47:26PM +0200, Andrew Jones wrote:
> > On Mon, Sep 16, 2013 at 11:55:17AM +0300, Gleb Natapov wrote:
> > > On Mon, Sep 16, 2013 at 10:22:09AM +0200, Andrew Jones wrote:
> > > > > > [1] Actually, until 972fc54
On Mon, Sep 16, 2013 at 03:21:47PM +0100, Mark Rutland wrote:
> On Thu, Sep 12, 2013 at 05:53:04PM +0100, Guenter Roeck wrote:
> > On Thu, Sep 12, 2013 at 05:41:00PM +0100, Mark Rutland wrote:
> > > On Fri, Aug 30, 2013 at 05:29:37AM +0100, Guenter Roeck wrote:
> > > > Signed-off-by: Guenter Roeck
On Tue, Sep 10, 2013 at 10:31:54AM +0100, Mel Gorman wrote:
> @@ -860,9 +908,14 @@ void task_numa_fault(int node, int pages, bool migrated)
>* If pages are properly placed (did not migrate) then scan slower.
>* This is reset periodically in case of phase changes
>*/
> -
On 09/16, Oleg Nesterov wrote:
>
> Unless task == current ptrace_parent(task) is not safe even under
> rcu_read_lock() and most of the current users are not right.
In particular selinux is buggy. But this needs another simple patch,
will do tomorrow.
> So may_change_ptraced_domain(task) looks wro
Hi Manish,
On Mon, Sep 16, 2013 at 08:20:16PM +0530, Manish Badarkhe wrote:
> @@ -1264,10 +1261,8 @@ static int mxt_remove(struct i2c_client *client)
> struct mxt_data *data = i2c_get_clientdata(client);
>
> sysfs_remove_group(&client->dev.kobj, &mxt_attr_group);
> - free_irq(dat
On Mon, Sep 16, 2013 at 4:41 AM, Tetsuo Handa
wrote:
> Kees Cook wrote:
>> - seq_printf(m, "%s%d%n", con->name, con->index, &len);
>> - len = 21 - len;
>> + len = m->count;
>> + seq_printf(m, "%s%d", con->name, con->index);
>> + len = 21 - (m->count - len);
>
> Why not to creat
Current code looks like this:
WARN_ON(lock_policy_rwsem_write(cpu));
update_policy_cpu(policy, new_cpu);
unlock_policy_rwsem_write(cpu);
{lock|unlock}_policy_rwsem_write(cpu) takes/releases policy->cpu's rwsem.
Because cpu is changing with the call to update_policy_cpu(),
lock_policy_rwsem_{read|write}() currently has return type of int but it always
return zero and hence its return type must be void instead. This patch makes its
return type void and fixes all users of it as well.
Reported-by: Jon Medhurst
Signed-off-by: Viresh Kumar
---
drivers/cpufreq/cpufreq.c
On Mon, 2013-09-16 at 07:59 -0700, Kees Cook wrote:
> Perhaps instead of seq->count, there should be an access function?
> seq_get_count(seq) or something?
My thought was to add a seq_last_len()
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message
On Mon, Sep 16, 2013 at 03:46:16PM +0100, Graeme Gregory wrote:
> On Mon, Sep 16, 2013 at 05:38:12PM +0300, Mika Westerberg wrote:
> > On Mon, Sep 16, 2013 at 11:12:49AM +0100, Mark Brown wrote:
> > > That's definitely an ACPI specific (probably x86 specific ACPI?)
> > > requirement not a generic o
On Mon, Sep 16, 2013 at 02:46:24PM +, KY Srinivasan wrote:
> > > + case VM_PKT_DATA_INBAND:
> > > + hv_kbd_on_receive(device, desc);
> >
> > This is the error handling I mentioned at the top. hv_kbd_on_receive()
> > doesn't take into consideration the a
> CC: "Johannes Weiner" , "Andrew Morton"
> , "David Rientjes" ,
> "KAMEZAWA Hiroyuki" , "KOSAKI Motohiro"
> , linux...@kvack.org,
> cgro...@vger.kernel.org, x...@kernel.org, linux-a...@vger.kernel.org,
> linux-kernel@vger.kernel.org
>On Mon 16-09-13 16:13:16, azurIt wrote:
>[...]
>> >You can
On Mon 16-09-13 16:13:16, azurIt wrote:
[...]
> >You can use sysrq+l via serial console to see tasks hogging the CPU or
> >sysrq+t to see all the existing tasks.
>
>
> Doesn't work here, it just prints 'l' resp. 't'.
I am using telnet for accessing my serial consoles exported by
the multiplicato
Hi,
> Is the Synchronous Serial Interface (SSI) only supported by
> OMAP34xx/OMAP35xx SoC and not by OMAP36xx/OMAP37xx SoC?
>
> I'm asking this since if SSI is supported by both we should add the
> device nodes in omap3.dtsi instead of omap34xx.dtsi.
>
> I thought that all OMAP3 SoC supported S
On Mon, Sep 16, 2013 at 09:52:26PM +0800, Xiao Guangrong wrote:
> Hi Gleb,
>
> On 09/16/2013 08:42 PM, Gleb Natapov wrote:
>
> >> static unsigned long *__gfn_to_rmap(gfn_t gfn, int level,
> >>struct kvm_memory_slot *slot)
> >> {
> >> @@ -4651,7 +4700,7 @@ int kvm
Update the code to use devm_* API so that driver core will manage
resources.
Signed-off-by: Manish Badarkhe
---
This is just clean up of code to manage resources using "devm_"
funtions. Not tested on hardware.
:100644 100644 59aa240... 73c5ad0... M drivers/input/touchscreen/atmel_mxt_ts.c
dri
On Mon, Sep 16, 2013 at 1:09 AM, Geert Uytterhoeven
wrote:
> On Mon, Sep 16, 2013 at 9:43 AM, Kees Cook wrote:
>> All users of %n are calculating padding size when using seq_file, so
>> instead use the new last_len member for discovering the length of the
>> written strings.
>
> Would it make sen
> -Original Message-
> From: Dan Carpenter [mailto:dan.carpen...@oracle.com]
> Sent: Monday, September 16, 2013 1:21 AM
> To: KY Srinivasan
> Cc: gre...@linuxfoundation.org; linux-kernel@vger.kernel.org;
> de...@linuxdriverproject.org; linux-in...@vger.kernel.org;
> dmitry.torok...@gmail.
On Mon, Sep 16, 2013 at 01:47:26PM +0200, Andrew Jones wrote:
> On Mon, Sep 16, 2013 at 11:55:17AM +0300, Gleb Natapov wrote:
> > On Mon, Sep 16, 2013 at 10:22:09AM +0200, Andrew Jones wrote:
> > > > > [1] Actually, until 972fc544b6034a in uq/master is merged there won't
> > > > > be
> > > > >
Update the code to use devm_* API so that driver core will manage
resources.
Signed-off-by: Manish Badarkhe
---
This is just clean up of code to manage resources using "devm_"
funtions. Not tested on hardware.
:100644 100644 bddabc5... 4ddf97c... M drivers/input/touchscreen/atmel_tsadcc.c
driv
On Mon, Sep 16, 2013 at 05:38:12PM +0300, Mika Westerberg wrote:
> On Mon, Sep 16, 2013 at 11:12:49AM +0100, Mark Brown wrote:
> > That's definitely an ACPI specific (probably x86 specific ACPI?)
> > requirement not a generic one, on some systems it would increase power
> > consumption since the co
On Mon, Sep 16, 2013 at 09:39:59AM -0400, Rik van Riel wrote:
> On 09/16/2013 08:36 AM, Peter Zijlstra wrote:
> > On Tue, Sep 10, 2013 at 10:31:47AM +0100, Mel Gorman wrote:
> >> A THP PMD update is accounted for as 512 pages updated in vmstat. This is
> >> large difference when estimating the cos
Naoya Horiguchi writes:
> Hi,
>
> Kirill posted split_ptl patchset for thp today, so in this version
> I post only hugetlbfs part. I added Kconfig variables in following
> Kirill's patches (although without CONFIG_SPLIT_*_PTLOCK_CPUS.)
>
> This patch changes many lines, but all are in hugetlbfs s
On Mon, Sep 16, 2013 at 11:12:49AM +0100, Mark Brown wrote:
> That's definitely an ACPI specific (probably x86 specific ACPI?)
> requirement not a generic one, on some systems it would increase power
> consumption since the controller will need to sit on while the device is
> functioning autonomous
This makes the interface more deterministic for userspace, which can expect
(after configuring only the features it supports) to get exactly the same
state from the kernel, independent of the host CPU and kernel version.
Suggested-by: Gleb Natapov
Signed-off-by: Paolo Bonzini
---
arch/x86/inclu
A guest can still attempt to save and restore XSAVE states even if they
have been masked in CPUID leaf 0Dh. This usually is not visible to
the guest, but is still wrong: "Any attempt to set a reserved bit (as
determined by the contents of EAX and EDX after executing CPUID with
EAX=0DH, ECX= 0H) in
Unless task == current ptrace_parent(task) is not safe even under
rcu_read_lock() and most of the current users are not right.
So may_change_ptraced_domain(task) looks wrong as well. However it
is always called with task == current so the code is actually fine.
Remove this argument to make this fa
XSAVE entries that KVM does not support are reported by
KVM_GET_SUPPORTED_CPUID for leaf 0Dh index 0 if the host supports them;
they should be left out unless there is also hypervisor support for them.
Sub-leafs are correctly handled in supported_xcr0_bit, fix index 0
to match.
Signed-off-by: Pao
As soon as the kernel will support the XSAVE extensions in Skylake
processors, we will want both userspace and the hypervisor to run
guests without showing any trace of the new features (because
support for them in the hypervisor will come later).
This series does exactly this. Patches 1 and 3 en
My Dear One,
I am glad to know you, but God knows you better and he knows why he has
directed me to you at this point in time, I know you will be amazed to read
from me, but do not be afraid, Rader to consider this letter as a request from
a old woman who is in needy of
your assistance. I am M
On Thu, Sep 12, 2013 at 09:17:05AM -0700, Greg KH wrote:
[..]
> Your paranoia is admirable in these patches. If they are accepted, that
> is a good first step, but what about the other kexec variants out there?
Any other kexec variant out there which are not statically compiled
will not work on
This platform driver adds the support of Secure Digital Host Controller
Interface compliant controller found in Qualcomm MSM chipsets.
CC: Asutosh Das
CC: Venkat Gopalakrishnan
CC: Sahitya Tummala
CC: Subhash Jadavani
Signed-off-by: Georgi Djakov
---
Changes from v4:
- Simplified sdhci_msm_vr
On Thu, Sep 12, 2013 at 05:53:04PM +0100, Guenter Roeck wrote:
> On Thu, Sep 12, 2013 at 05:41:00PM +0100, Mark Rutland wrote:
> > On Fri, Aug 30, 2013 at 05:29:37AM +0100, Guenter Roeck wrote:
> > > Signed-off-by: Guenter Roeck
> > > ---
> > > .../devicetree/bindings/extcon/extcon-gpio |
On Mon, Sep 16, 2013 at 02:03:33PM +0200, Andrew Jones wrote:
> On Mon, Sep 16, 2013 at 11:47:10AM +0300, Gleb Natapov wrote:
> > On Mon, Sep 16, 2013 at 10:28:20AM +0200, Andrew Jones wrote:
> > > On Sun, Sep 15, 2013 at 12:08:38PM +0300, Gleb Natapov wrote:
> > > > On Sat, Sep 14, 2013 at 02:18:4
> CC: "Johannes Weiner" , "Andrew Morton"
> , "David Rientjes" ,
> "KAMEZAWA Hiroyuki" , "KOSAKI Motohiro"
> , linux...@kvack.org,
> cgro...@vger.kernel.org, x...@kernel.org, linux-a...@vger.kernel.org,
> linux-kernel@vger.kernel.org
>On Mon 16-09-13 16:01:19, azurIt wrote:
>> > CC: "Johannes
Commit-ID: 13b62e46d5407c7d619aea1dc9c3e0991b631b57
Gitweb: http://git.kernel.org/tip/13b62e46d5407c7d619aea1dc9c3e0991b631b57
Author: Michael S. Tsirkin
AuthorDate: Mon, 16 Sep 2013 11:30:36 +0300
Committer: Ingo Molnar
CommitDate: Mon, 16 Sep 2013 11:18:34 +0200
sched: Fix comment fo
Paul Gortmaker reported a BUG on preempt-rt kernels, due to taking the
mmu_lock within the raw kvm_lock in mmu_shrink_scan. He provided a
patch that shrunk the kvm_lock critical section so that the mmu_lock
critical section does not nest with it, but in the end there is no reason
for the vm_list t
Remove the useless argument, and do not do anything if there are no
VMs running at the time of the hotplug.
Cc: sta...@vger.kernel.org
Cc: k...@vger.kernel.org
Cc: g...@redhat.com
Cc: jan.kis...@siemens.com
Signed-off-by: Paolo Bonzini
---
virt/kvm/kvm_main.c | 14 --
1 file changed,
The VM list need not be protected by a raw spinlock. Separate the
two so that kvm_lock can be made non-raw.
Cc: sta...@vger.kernel.org
Cc: k...@vger.kernel.org
Cc: g...@redhat.com
Cc: jan.kis...@siemens.com
Signed-off-by: Paolo Bonzini
---
Documentation/virtual/kvm/locking.txt | 6 +-
virt
In commit e935b8372cf8 ("KVM: Convert kvm_lock to raw_spinlock"),
the kvm_lock was made a raw lock. However, the kvm mmu_shrink()
function tries to grab the (non-raw) mmu_lock within the scope of
the raw locked kvm_lock being held. This leads to the following:
BUG: sleeping function called from
On Mon 16-09-13 16:01:19, azurIt wrote:
> > CC: "Johannes Weiner" , "Andrew Morton"
> > , "David Rientjes" ,
> > "KAMEZAWA Hiroyuki" , "KOSAKI Motohiro"
> > , linux...@kvack.org,
> > cgro...@vger.kernel.org, x...@kernel.org, linux-a...@vger.kernel.org,
> > linux-kernel@vger.kernel.org
> >On Sa
[Sorry for the late reply. I am in pre-long-vacation mode trying to
clean up my desk]
On Thu 12-09-13 08:59:38, Johannes Weiner wrote:
> On Mon, Sep 09, 2013 at 02:56:59PM +0200, Michal Hocko wrote:
[...]
> > Hmm, wait a second. I have completely forgot about the kmem charging
> > path during the
> CC: "Johannes Weiner" , "Andrew Morton"
> , "David Rientjes" ,
> "KAMEZAWA Hiroyuki" , "KOSAKI Motohiro"
> , linux...@kvack.org,
> cgro...@vger.kernel.org, x...@kernel.org, linux-a...@vger.kernel.org,
> linux-kernel@vger.kernel.org
>On Sat 14-09-13 12:48:31, azurIt wrote:
>[...]
>> Here is t
Hi,
On Mon, 2013-09-16 at 15:35 +0200, Miklos Szeredi wrote:
> On Mon, Sep 16, 2013 at 02:17:49PM +0100, Steven Whitehouse wrote:
> > Hi,
> >
> > On Mon, 2013-09-16 at 14:52 +0200, Miklos Szeredi wrote:
> > > From: Miklos Szeredi
> > >
> > > unless it was given an IS_ERR(inode), which isn't the
Hi,
On Mon, 2013-09-16 at 15:34 +0200, Miklos Szeredi wrote:
> On Mon, Sep 16, 2013 at 02:13:14PM +0100, Steven Whitehouse wrote:
> > Hi,
> >
> > On Mon, 2013-09-16 at 14:52 +0200, Miklos Szeredi wrote:
> > > From: Miklos Szeredi
> > >
> > > AFAICS if d_splice_alias() returned non-NULL, this co
Prototype of two functions added to the header to avoid the use of extern.
Signed-off-by: Iker Pedrosa
---
drivers/staging/winbond/mto.c | 4 +---
drivers/staging/winbond/mto.h | 4 ++--
2 files changed, 3 insertions(+), 5 deletions(-)
diff --git a/drivers/staging/winbond/mto.c b/drivers/stagin
Deleted declaration of external functions that weren't used on this driver.
Signed-off-by: Iker Pedrosa
---
drivers/staging/winbond/mto.h | 4
1 file changed, 4 deletions(-)
diff --git a/drivers/staging/winbond/mto.h b/drivers/staging/winbond/mto.h
index 22bb264..8d41eed 100644
--- a/drive
Hi Gleb,
On 09/16/2013 08:42 PM, Gleb Natapov wrote:
>> static unsigned long *__gfn_to_rmap(gfn_t gfn, int level,
>> struct kvm_memory_slot *slot)
>> {
>> @@ -4651,7 +4700,7 @@ int kvm_mmu_module_init(void)
>> {
>> pte_list_desc_cache = kmem_cache_create("
On Mon, Sep 16, 2013 at 02:44:35PM +0200, Linus Walleij wrote:
> I've tried to fix this for DT-only I2C devices
> and this very driver was the reason.
> But a tiresome regression due to drivers relying on this
> i2c_device_id not being NULL and inability to remove it from the I2C
> core without r
[update Kent's email address]
On Mon, Sep 16, 2013 at 7:40 AM, Bjorn Helgaas wrote:
> On Thu, Jun 13, 2013 at 12:33 PM, Kent Overstreet
> wrote:
>> On Thu, Jun 13, 2013 at 12:14:54PM -0600, Bjorn Helgaas wrote:
>>> On Wed, May 29, 2013 at 4:29 PM, Bjorn Helgaas wrote:
>>> > This fixes a copy an
The following function declarations have been removed because they aren't
implemented.
Signed-off-by: Iker Pedrosa
---
drivers/staging/winbond/mto.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/staging/winbond/mto.c b/drivers/staging/winbond/mto.c
index 560c0ab..0d0f9fb 100644
301 - 400 of 613 matches
Mail list logo
