At the moment there are a lot of places that handle setting or getting
the page cache mode by treating the pgprot bits equal to the cache mode.
This is only true because there are a lot of assumptions about the setup
of the PAT MSR. Otherwise the cache type needs to get translated into
pgprot bits
The x86 architecture offers via the PAT (Page Attribute Table) a way to
specify different caching modes in page table entries. The PAT MSR contains
8 entries each specifying one of 6 possible cache modes. A pte references one
of those entries via 3 bits: _PAGE_PAT, _PAGE_PWT and _PAGE_PCD.
The Lin
Update the translation tables from cache mode to pgprot values
according to the PAT settings. This enables changing the cache
attributes of a PAT index in just one place without having to change
at the users side.
With this change it is possible to use the same kernel with different
PAT configurat
With the dynamical mapping between cache modes and pgprot values it is
now possible to use all cache modes via the Xen hypervisor PAT settings
in a pv domain.
All to be done is to read the PAT configuration MSR and set up the
translation tables accordingly.
Signed-off-by: Juergen Gross
Reviewed-
On Mon, 2014-10-27 at 14:37 +0800, Wang, Yalin wrote:
> this change add CONFIG_HAVE_ARCH_BITREVERSE config option,
> so that we can use arm/arm64 rbit instruction to do bitrev operation
> by hardware.
>
> Signed-off-by: Yalin Wang
> ---
> arch/arm/Kconfig| 1 +
> arch/arm/includ
On Tue, Oct 07, 2014 at 05:33:35PM +0200, Vlastimil Babka wrote:
> Compaction relies on zone watermark checks for decisions such as if it's worth
> to start compacting in compaction_suitable() or whether compaction should stop
> in compact_finished(). The watermark checks take classzone_idx and all
Joe Perches writes:
> On Mon, 2014-10-27 at 07:16 +0100, Jes Sorensen wrote:
>> Joe Perches writes:
>> > On Mon, 2014-10-27 at 06:45 +0100, Jes Sorensen wrote:
>> >> Joe Perches writes:
>> >> > On Sun, 2014-10-26 at 16:18 +, Paul McQuade wrote:
>> >> >> ERROR: spaces required around that ':'
On Mon, 2014-27-10 at 04:24:35 UTC, Ian Munsie wrote:
> From: Ian Munsie
>
> In certain circumstances the PSL can send an interrupt for a segment
Define PSL before using it please.
> miss that the kernel has already handled. This can happen if multiple
> translations for the same segment are qu
this change add CONFIG_HAVE_ARCH_BITREVERSE config option,
so that we can use arm/arm64 rbit instruction to do bitrev operation
by hardware.
Signed-off-by: Yalin Wang
---
arch/arm/Kconfig| 1 +
arch/arm/include/asm/bitrev.h | 21 +
arch/arm64/Kconfig
On Sun, 26 Oct 2014 17:41:37 -0700
Casey Schaufler wrote:
> On 10/17/2014 10:37 AM, Casey Schaufler wrote:
> > On 10/17/2014 9:34 AM, PINTU KUMAR wrote:
> >> Hi,
> >>
> >>
> >>>
> >>> From: Casey Schaufler
> >>> To: Rohit
> >>> Cc: a...@linux-foundation.org; ja
Sorry for butting in, but as a concerned user, let me add my two cents.
I have just about enough expertise in kernel to port this patch to
newer kernel versions. I have absolutely no idea on how to fix this
proper. And porting (in my case) is time-consuming and error-prone.
I wish this patch was
On 2014/10/24 23:36, Peter Zijlstra wrote:
> On Tue, Oct 21, 2014 at 11:15:10PM +0800, Li, Aubrey wrote:
>> +++ b/arch/x86/kernel/apic/apic.c
>> @@ -917,6 +917,14 @@ static void local_apic_timer_interrupt(void)
>> */
>> inc_irq_stat(apic_timer_irqs);
>>
>> +/*
>> + * if timekee
On Mon, 2014-10-27 at 07:16 +0100, Jes Sorensen wrote:
> Joe Perches writes:
> > On Mon, 2014-10-27 at 06:45 +0100, Jes Sorensen wrote:
> >> Joe Perches writes:
> >> > On Sun, 2014-10-26 at 16:18 +, Paul McQuade wrote:
> >> >> ERROR: spaces required around that ':' (ctx:VxE)
> > []
> >> >> di
Joe Perches writes:
> On Mon, 2014-10-27 at 06:45 +0100, Jes Sorensen wrote:
>> Joe Perches writes:
>> > On Sun, 2014-10-26 at 16:18 +, Paul McQuade wrote:
>> >> ERROR: spaces required around that ':' (ctx:VxE)
> []
>> >> diff --git a/drivers/staging/rtl8723au/core/rtw_ieee80211.c
>> >> b/dri
>
> Precedence of & and >> is not the same and is not left to right.
> shift has higher precedence and should be done after the mask.
>
> Add parentheses around the mask.
>
> Signed-off-by: Joe Perches
> ---
Applied - thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-k
On Mon, 2014-10-27 at 06:45 +0100, Jes Sorensen wrote:
> Joe Perches writes:
> > On Sun, 2014-10-26 at 16:18 +, Paul McQuade wrote:
> >> ERROR: spaces required around that ':' (ctx:VxE)
[]
> >> diff --git a/drivers/staging/rtl8723au/core/rtw_ieee80211.c
> >> b/drivers/staging/rtl8723au/core/r
The kernel uses 32-bit signed value(time_t) for seconds since
1970-01-01:00:00:00, thus it
will overflow at 2038-01-19 03:14:08 on 32-bit systems. We call this "2038
safety" issue.
As part of addressing 2038 saftey for in-kernel uses, this patch adds the safe
rtc_tm_to_time()
using time64_t. Af
The kernel uses 32-bit signed value(time_t) for seconds since
1970-01-01:00:00:00, so it
will overflow at 2038-01-19 03:14:08 on 32-bit systems. We call this "2038
safety" issue.
This patch fixed the build warnings brought by former patches.
Signed-off-by: pang.xunlei
---
include/linux/time64
The kernel uses 32-bit signed value(time_t) for seconds since
1970-01-01:00:00:00, so it
will overflow at 2038-01-19 03:14:08 on 32-bit systems. We call this "2038
safety" issue.
As part of addressing 2038 saftey for in-kernel uses, this patch creates no
functional change
in existing users, and
The kernel uses 32-bit signed value(time_t) for seconds since
1970-01-01:00:00:00, so it
will overflow at 2038-01-19 03:14:08 on 32-bit systems. We call this "2038
safety" issue.
As part of addressing 2038 safety for in-kernel uses, this patch creates no
functional change
in existing users, con
The kernel uses 32-bit signed value(time_t) for seconds since
1970-01-01:00:00:00, so it
will overflow at 2038-01-19 03:14:08 on 32-bit systems. We call this "2038
safety" issue.
As part of addressing 2038 safety for in-kernel uses, this patch creates no
functional change
in existing users, con
The kernel uses 32-bit signed value(time_t) for seconds since
1970-01-01:00:00:00, thus it
will overflow at 2038-01-19 03:14:08 on 32-bit systems. We call this "2038
safety" issue.
As part of addressing 2038 saftey for in-kernel uses, this patch adds the safe
rtc_time_to_tm()
using time64_t. Af
The kernel uses 32-bit signed value(time_t) for seconds since
1970-01-01:00:00:00, so it
will overflow at 2038-01-19 03:14:08 on 32-bit systems. We call this "2038
safety" issue.
As part of addressing 2038 saftey for in-kernel uses, this patch creates no
functional change
in existing users, and
The kernel uses 32-bit signed value(time_t) for seconds since
1970-01-01:00:00:00, thus it
will overflow at 2038-01-19 03:14:08 on 32-bit systems. We call this "2038
safety" issue.
Currently, rtc_time_to_tm() deals with "unsigned long" which is 2038 unsafe on
32-bit systems.
As part of address
The kernel uses 32-bit signed value(time_t) for seconds since
1970-01-01:00:00:00, thus it
will overflow at 2038-01-19 03:14:08 on 32-bit systems. We call this "2038
safety" issue.
As part of addressing 2038 saftey for in-kernel uses, this patch adds the safe
mktime() using
time64_t. After this
The kernel uses 32-bit signed value(time_t) for seconds since
1970-01-01:00:00:00, so it
will overflow at 2038-01-19 03:14:08 on 32-bit systems. We call this "2038
safety" issue.
As part of addressing 2038 safety for in-kernel uses, convert do_settimeofday()
to use the timespec64 structure, and
The kernel uses 32-bit signed value(time_t) for seconds since
1970-01-01:00:00:00, thus it
will overflow at 2038-01-19 03:14:08 on 32-bit systems. We call this "2038
safety" issue.
Currently, rtc_tm_to_time() deals with "unsigned long" which is 2038 unsafe on
32-bit systems.
As part of address
Could you review my patch?
Thanks,
Yasuaki Ishimatsu
(2014/10/22 16:04), Yasuaki Ishimatsu wrote:
> While offling node by hot removing memory, the following divide error
> occurs:
>
>divide error: [#1] SMP
>[...]
>Call Trace:
> [...] handle_mm_fault
> [...] ? try_to_wake
The kernel uses 32-bit signed value(time_t) for seconds since
1970-01-01:00:00:00, thus it
will overflow at 2038-01-19 03:14:08 on 32-bit systems. We call this "2038
safety" issue.
Currently, mktime() deals with "unsigned long" which is 2038 unsafe on 32-bit
systems.
As part of addressing 2038
Paul McQuade writes:
> create marco for max_rate values
>
> Signed-off-by: Paul McQuade
> ---
> drivers/staging/rtl8723au/core/rtw_ieee80211.c | 58
> --
> 1 file changed, 26 insertions(+), 32 deletions(-)
>
> diff --git a/drivers/staging/rtl8723au/core/rtw_ieee80211.c
The kernel uses 32-bit signed value(time_t) for seconds since
1970-01-01:00:00:00, so it
will overflow at 2038-01-19 03:14:08 on 32-bit systems. We call this "2038
safety" issue.
This series doesn't involve any functional change, and mainly converts
do_settimeofday()
to use timespec64. During t
Joe Perches writes:
> On Sun, 2014-10-26 at 16:18 +, Paul McQuade wrote:
>> ERROR: spaces required around that ':' (ctx:VxE)
>>
>> Signed-off-by: Paul McQuade
>> ---
>> drivers/staging/rtl8723au/core/rtw_ieee80211.c | 16
>> 1 file changed, 8 insertions(+), 8 deletions(-)
>
Mark these as subscriber-only mailing lists.
Signed-off-by: Joe Perches
---
I got rejects not moderation emails for patches to these lists...
MAINTAINERS | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 1b063fc..2e353c7 100644
--- a/MAINTAI
Shift has a higher precedence that mask so warn
when a mask then shift operation is done without
parentheses around the mask.
This test works well for a right shift, but the
left shift is pretty commonly done correctly so
only warn on the right shift.
Signed-off-by: Joe Perches
---
scripts/chec
Precedence of & and >> is not the same and is not left to right.
shift has higher precedence and should be done after the mask.
Here the shifts are unnecessary and a non-zero value can be used
as the test to set 1 or zero.
Signed-off-by: Joe Perches
---
drivers/input/tablet/aiptek.c | 6 +++---
Precedence of & and >> is not the same and is not left to right.
shift has higher precedence and should be done after the mask.
Add parentheses around the mask.
Use the already #defined values instead of hardcoding.
Signed-off-by: Joe Perches
---
drivers/gpu/drm/radeon/evergreen.c | 3 ++-
1 f
logical mask has lower precedence than shift but should be
done before the shift so parentheses are generally required.
And when masking with a fixed value after a shift, normal kernel
style has the shift on the left, then the shift on the right so
convert a few non-conforming uses.
Joe Perches (
Precedence of & and >> is not the same and is not left to right.
shift has higher precedence and should be done after the mask.
Add parentheses around the mask.
Signed-off-by: Joe Perches
---
drivers/mfd/wm8350-core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/m
Precedence of & and >> is not the same and is not left to right.
shift has higher precedence and should be done after the mask.
Add parentheses around the mask.
Signed-off-by: Joe Perches
---
drivers/block/nvme-scsi.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --gi
Precedence of & and >> is not the same and is not left to right.
shift has higher precedence and should be done after the mask.
Add parentheses around the mask.
Signed-off-by: Joe Perches
---
sound/pci/ad1889.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/sound/pc
Precedence of & and >> is not the same and is not left to right.
shift has higher precedence and should be done after the mask.
Add parentheses around the mask.
Signed-off-by: Joe Perches
---
drivers/ssb/driver_chipcommon_pmu.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --g
Precedence of & and >> is not the same and is not left to right.
shift has higher precedence and should be done after the mask.
Add parentheses around the mask.
Signed-off-by: Joe Perches
---
drivers/net/wireless/iwlwifi/dvm/lib.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff
Precedence of & and >> is not the same and is not left to right.
shift has higher precedence and should be done after the mask.
Add parentheses around the masks.
Signed-off-by: Joe Perches
---
drivers/tty/ipwireless/hardware.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
Precedence of & and >> is not the same and is not left to right.
shift has higher precedence and should be done after the mask.
Add parentheses around the mask.
Signed-off-by: Joe Perches
---
drivers/usb/host/hwa-hc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/u
Precedence of & and >> is not the same and is not left to right.
shift has higher precedence and should be done after the mask.
This use has a mask then shift which is not the normal style.
Move the shift before the mask to match nearly all the other
uses in kernel.
Signed-off-by: Joe Perches
-
Precedence of & and >> is not the same and is not left to right.
shift has higher precedence and should be done after the mask.
Add parentheses around the mask.
Signed-off-by: Joe Perches
---
drivers/media/dvb-core/dvb_net.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a
Fix minor syntax issues in processor_core.c to follow coding styles.
Signed-off-by: Jiang Liu
---
drivers/acpi/processor_core.c |9 -
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/drivers/acpi/processor_core.c b/drivers/acpi/processor_core.c
index ef58f46c8442..342942
Implement acpi_unregister_ioapic() to support ACPI based IOAPIC hot-removal.
An IOAPIC could only be removed when all its pins are unused.
Signed-off-by: Jiang Liu
---
arch/x86/include/asm/io_apic.h |1 +
arch/x86/kernel/acpi/boot.c| 13 +++---
arch/x86/kernel/apic/io_apic.c | 55
We are going to support ACPI based IOAPIC hotplug, so introduce a rwsem
to protect IOAPIC data structures from IOAPIC hotplug. We choose to
serialize in ACPI instead of in the IOAPIC core because:
1) currently we are only plan to support ACPI based IOAPIC hotplug
2) it's much more cleaner and easie
Enable support of IOAPIC hotplug by:
1) reintroducing ACPI based IOAPIC driver
2) enhance pci_root driver to hook hotplug events
The ACPI IOAPIC driver is always enabled if all of ACPI, PCI and IOAPIC
are enabled.
Signed-off-by: Jiang Liu
---
drivers/acpi/Kconfig|6 ++
drivers/acpi/Make
On Sat, Oct 25, 2014 at 7:05 AM, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> Provide a way for device drivers using GPIOs described by ACPI
> GpioIo resources in _CRS to tell the GPIO subsystem what names
> (connection IDs) to associate with specific GPIO pins defined
> in there.
>
> T
Introduce acpi_ioapic_registered() to check whether an IOAPIC has already
been registered, it will be used when enabling IOAPIC hotplug.
Signed-off-by: Jiang Liu
---
arch/x86/include/asm/io_apic.h |1 +
arch/x86/kernel/acpi/boot.c| 22 ++
arch/x86/kernel/apic/io_api
Refine mp_register_ioapic() to prepare for IOAPIC hotplug by:
1) change return value from void to int.
2) check for gsi range conflicts
3) check for IOAPIC physical address conflicts
4) enhance the way to allocate IOAPIC index
Signed-off-by: Jiang Liu
---
arch/x86/include/asm/io_apic.h |4 +-
Implement acpi_register_ioapic() and enhance mp_register_ioapic()
to support ACPI based IOAPIC hot-addition.
Signed-off-by: Jiang Liu
---
arch/x86/kernel/acpi/boot.c| 31 +--
arch/x86/kernel/apic/io_apic.c | 22 +-
2 files changed, 50 inser
To keep balance of IOAPIC pin reference count, we need to protect
pirq_enable_irq(), acpi_pci_irq_enable() and intel_mid_pci_irq_enable()
from reentrance. There are two cases which will cause reentrance.
The first case is caused by suspend/hibernation. If pcibios_disable_irq
is called during suspe
Remove __init marker for functions which will be used by IOAPIC hotplug
at runtime.
Signed-off-by: Jiang Liu
---
arch/x86/include/asm/io_apic.h |4 ++--
arch/x86/kernel/apic/io_apic.c | 18 +-
2 files changed, 11 insertions(+), 11 deletions(-)
diff --git a/arch/x86/include
From: Yinghai Lu
We need to parse APIC ID for IOAPIC registration for IOAPIC hotplug.
ACPI _MAT method and MADT table are used to figure out IOAPIC ID, just
like parsing CPU APIC ID for CPU hotplug.
Signed-off-by: Yinghai Lu
Signed-off-by: Jiang Liu
---
drivers/acpi/processor_core.c | 122 ++
From: Yinghai Lu
Split out alloc_ioapic_save_registers() from early_irq_init(),
so it could be used for ioapic hotplug later.
Signed-off-by: Yinghai Lu
Signed-off-by: Jiang Liu
Cc: Joerg Roedel
Cc: Konrad Rzeszutek Wilk
Cc: Sebastian Andrzej Siewior
---
arch/x86/kernel/apic/io_apic.c | 2
From: Yinghai Lu
Perfer the assigned ID in APIC ID register for x86_64 if it's still
available.
Signed-off-by: Yinghai Lu
Cc: Joerg Roedel
Cc: Konrad Rzeszutek Wilk
Cc: Sebastian Andrzej Siewior
Signed-off-by: Jiang Liu
---
arch/x86/kernel/apic/io_apic.c | 35
To support IOAPIC hotplug on x86 and IA64 platforms, OS needs to figure
out global interrupt source number(GSI) and IOAPIC enumeration ID
through ACPI interfaces. So BIOS must implement an ACPI IOAPIC device
with _GSB/_UID or _MAT method to support IOAPIC hotplug. OS also needs
to figure out base p
Change acpi_dev_resource_address_space() to return failure if the
acpi_resource structure can't be converted to an ACPI address64
structure, so caller could correctly detect failure.
Signed-off-by: Jiang Liu
---
drivers/acpi/resource.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
di
Private function resource_to_addr() is used to parse ACPI resources
for PCI host bridge. There are public interfaces available for that
purpose, so replace resource_to_addr() with public interfaces.
Reviewed-by: Bjorn Helgaas
Signed-off-by: Jiang Liu
---
arch/x86/pci/acpi.c | 144 +
The GSI for ACPI SCI may be shared with other devices. For example,
Function mp_register_gsi() should return IRQ number, so fix a regression
by returning mp_map_gsi_to_irq(gsi, 0) instead of gsi.
The regression was caused by commit 84245af7297ced9e8fe "x86, irq, ACPI:
Change __acpi_register_gsi t
Intel MID platforms has no legacy interrupts, so no IRQ descriptors
preallocated. We need to call mp_map_gsi_to_irq() to create IRQ
descriptors for APB timers and RTC timers, otherwise it may cause
invalid memory access as:
[0.116839] BUG: unable to handle kernel NULL pointer dereference at
000
When IOAPIC is disabled, acpi_gsi_to_irq() should return gsi directly
instead of calling mp_map_gsi_to_irq() to translate gsi to IRQ by IOAPIC.
It fixes https://bugzilla.kernel.org/show_bug.cgi?id=84381.
Reported-by: Thomas Richter
Signed-off-by: Jiang Liu
Cc: rui.zh...@intel.com
Cc: # 3.17
---
This patch set enhances IOAPIC core and ACPI drivers to support IOAPIC
hotplug on x86 platforms. It's based on v3.18-rc2 at
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
You may pull it from
https://github.com/jiangliu/linux.git ioapic/hotplug_v7
We have pick up several patc
This patch set enhances IOAPIC core and ACPI drivers to support IOAPIC
hotplug on x86 platforms. It's based on v3.18-rc2 at
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
You may pull it from
https://github.com/jiangliu/linux.git ioapic/hotplug_v7
We have pick up several patc
Hi all,
Changes since 20141023:
New trees: thermal-soc, y2038
The bluetooth tree gained a build failure so I used the version from
next-20141023.
The sound-asoc tree lost its build failure.
The pinctrl tree gained a build failure so I used the version from
next-20141023.
The akpm-current tree
The following patch adds a function to return tv_sec portion of
ktime_get_real_ts64() function in order to have a function that returns
seconds as 64-bit integers instead of 32-bit integers to address the
y2038 problem.
The function is similar to get_seconds() function except that it
includes read
On Fri, Oct 24, 2014 at 11:29 PM, Daniel Thompson
wrote:
> irq_set_irq_wake() treats its second argument as a boolean. It is much
> easier to read code when constant booleans are either 0 or 1!
>
> This particular line of code distracted me somewhat when I was doing a bit of
> work in a code brows
Hi Andrew,
After merging the akpm-current tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
mm/cma.c: In function 'cma_declare_contiguous':
mm/cma.c:288:4: error: implicit declaration of function 'phys_to_virt'
[-Werror=implicit-function-declaration]
kmemleak_ignore(
From: Ian Munsie
In certain circumstances the PSL can send an interrupt for a segment
miss that the kernel has already handled. This can happen if multiple
translations for the same segment are queued in the PSL before the
kernel has restarted the first translation.
The CXL driver did not expect
I noticed that nanosleep() on 64 bit, "only" supports 292 years,
rather than the full potential 292 billion years with 64 bit time_t, due to:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/include/linux/time.h?id=refs/tags/v3.16#n87
Attached is a program from Paul Eggert that
On 10/26/2014 07:41 PM, Andrew Lunn wrote:
On Sun, Oct 26, 2014 at 09:52:39AM -0700, Guenter Roeck wrote:
On some chips it is possible to access the switch eeprom.
Add infrastructure support for it.
Signed-off-by: Guenter Roeck
---
v2:
- Add support for configuring switch EEPROM size through p
> -Original Message-
> From: Viresh Kumar [mailto:viresh.ku...@linaro.org]
> Sent: Tuesday, October 21, 2014 5:04 PM
> To: Tang Yuantian-B29983
> Cc: Rafael J. Wysocki; Linux Kernel Mailing List; linux...@vger.kernel.org;
> linuxppc-...@ozlabs.org
> Subject: Re: [PATCH] cpufreq: qoriq: Mak
Hi Linus,
After merging the pinctrl tree, today's linux-next build (arm
multi_v7_defconfig)
failed like this:
drivers/pinctrl/samsung/pinctrl-exynos.c:1194:43: error: array type has
incomplete element type
static const struct samsung_pin_bank_data exynos7_pin_banks0[] __initconst = {
On 10/24/2014 08:08 PM, Thomas Gleixner wrote:
On Sun, 12 Oct 2014, Qiaowei Ren wrote:
+ /*
+* Go poke the address of the new bounds table in to the
+* bounds directory entry out in userspace memory. Note:
+* we may race with another CPU instantiating the same tabl
On Fri, Oct 24, 2014 at 10:35:29AM -0600, Bjorn Helgaas wrote:
> On Fri, Oct 17, 2014 at 04:53:27PM +0800, Huang Rui wrote:
> > The dwc3 controller is the PCI-E device in AMD NL platform, but the class
> > code
> > of PCI header is 0x0c0330, the same with xHC. That's because it needs to
> > meet
On 10/24/2014 10:40 PM, Thomas Gleixner wrote:
On Sun, 12 Oct 2014, Qiaowei Ren wrote:
Since we are doing the freeing from munmap() (and other paths like it),
we hold mmap_sem for write. If we fault, the page fault handler will
attempt to acquire mmap_sem for read and we will deadlock. For now,
Idle cpu is idler than non-idle cpu, so we needn't loop non-idle cpus after
find an idle cpu.
Signed-off-by:yaodongd...@huawei.com
---
kernel/sched/fair.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
index 0b069bf..2445a23 100644
Hi,
Thanks for letting me know.
Though IMO the ACER behavior is not ACPI spec compliant, but following it still
shouldn't break the others.
Because it just requires EC firmware to always flag SCI_EVT when there is an
event queued up.
I couldn't see a special reason that a correct EC firmware sh
The Yoga 3 does not contain any physical rfkill switch. Therefore
disable the rfkill switch identically to the Yoga 2 approach.
Signed-off-by: Stephan Mueller
---
drivers/platform/x86/ideapad-laptop.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/drivers/platform/x86/ideapad-laptop
The current per-cpu offline info won't be updated when we use
any other method besides sysfs to call cpu_up/down.
Thus the cpu/online can't reflect the real online status.
This patch is going to fix the issue introduced by commit
0902a9044fa5b7a0456ea4daacec2c2b3189ba8c (Driver core:
Use generic o
On Mon, 2014-10-27 at 10:04 +0800, kernel test robot wrote:
> FYI, we noticed the below changes on
>
> commit eea203fea3484598280a07fe503e025e886297fb ("rcu: Use pr_alert/pr_cont
> for printing logs")
>
>
> +--++---
From: Eric Dumazet
Date: Thu, 23 Oct 2014 06:30:30 -0700
> From: Eric Dumazet
>
> Do not reuse skb if it was pfmemalloc tainted, otherwise
> future frame might be dropped anyway.
>
> Signed-off-by: Eric Dumazet
Applied, thanks Eric.
--
To unsubscribe from this list: send the line "unsubscrib
This add the necessary binding documentation for the thermal
found on Rockchip SoCs
Signed-off-by: zhaoyifeng
Signed-off-by: Caesar Wang
---
.../bindings/thermal/rockchip-thermal.txt | 53 ++
1 file changed, 53 insertions(+)
create mode 100644
Documentation/device
On Sun, Oct 26, 2014 at 09:52:39AM -0700, Guenter Roeck wrote:
> On some chips it is possible to access the switch eeprom.
> Add infrastructure support for it.
>
> Signed-off-by: Guenter Roeck
> ---
> v2:
> - Add support for configuring switch EEPROM size through platform data
> or devicetree d
This series patchs tested on rk3288 SDK board and pinky-v1,v2 board.
I believe the driver can be used on the rk3288-evb board.
Add this driver, The system can reset the entire chip when
the thermal temperture over 120C, In case of rising over 125C
when tha hardware shorting,The sodftware will shut
when a thermal temperature over TSHUT.Default to via
CRU reset the entire chip on rk3288-evb Board,
TSHUT is low active on rk3288-evb board.
Signed-off-by: Caesar Wang
---
arch/arm/boot/dts/rk3288-evb.dtsi | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/boot/dts/rk3288-evb.dts
This patch changes a dtsi file to contain the thermal data
on RK3288 and later SoCs. This data will
enable a thermal shutdown over 120C.
Signed-off-by: Caesar Wang
---
arch/arm/boot/dts/rk3288-thermal.dtsi | 65 +++
1 file changed, 65 insertions(+)
create mode 10
This patch is depend on rk3288-thermal.dtsi,or
it will compile error.
If for some reason we are unable to shut it down
in orderly fashion (kernel is stuck holding a lock or
similar), then hardware TSHUT will reset it.
If the temperature over a period of time High,over 125C
the resulting TSHUT gav
Thermal is TS-ADC Controller module supports
user-defined mode and automatic mode.
User-defined mode refers,TSADC all the control signals entirely by
software writing to register for direct control.
Automaic mode refers to the module automatically poll TSADC output,
and the results were checked.I
git commit b4f0d3755c5e9cc86292d5fd78261903b4f23d4a was very very dumb.
It was writing over %esp/pt_regs semi-randomly on i686 with the expected
"system can't boot" results. As noted in:
https://bugs.freedesktop.org/show_bug.cgi?id=85277
This patch stops fscking with pt_regs. Instead it sets up
> -Original Message-
> From: Greg KH [mailto:gre...@linuxfoundation.org]
> Sent: 2014年10月27日 10:27
> To: Neil Zhang
> Cc: Dan Streetman; linux-kernel@vger.kernel.org
> Subject: Re: [PATCH] drivers: base: update cpu offline info when do hotplug
>
> On Sun, Oct 26, 2014 at 07:17:14PM -0700
On Sun, Oct 26, 2014 at 07:17:14PM -0700, Neil Zhang wrote:
>
>
> > -Original Message-
> > From: Greg KH [mailto:gre...@linuxfoundation.org]
> > Sent: 2014年10月27日 9:59
> > To: Neil Zhang
> > Cc: Dan Streetman; linux-kernel@vger.kernel.org
> > Subject: Re: [PATCH] drivers: base: update cpu
FYI, we noticed the below changes on
commit f3ca4164529b875374c410193bbbac0ee960895f ("ACPI / processor: Rework
processor throttling with work_on_cpu()")
v3.14-rc4 f3ca4164529b875374c410193b testbox/testcase/testparams
-- -
On Mon, 2014-10-27 at 10:18 +0800, kernel test robot wrote:
> FYI, we noticed the below changes on
>
> commit 76835b0ebf8a7fe85beb03c75121419a7dec52f0 ("futex: Ensure
> get_futex_key_refs() always implies a barrier")
fwiw I was also able to reproduce similar results, with the hashing
costing (un
Hi Gustavo,
After merging the bluetooth tree, today's linux-next build (x86_64
allmodconfig) failed like this:
net/bluetooth/smp.o: In function `test_smp':
smp.c:(.init.text+0x0): multiple definition of `init_module'
net/bluetooth/af_bluetooth.o:af_bluetooth.c:(.init.text+0x0): first defined here
On 2014-10-24, Thomas Gleixner wrote:
> On Sun, 12 Oct 2014, Qiaowei Ren wrote:
>> +int mpx_enable_management(struct task_struct *tsk) {
>> +struct mm_struct *mm = tsk->mm;
>> +void __user *bd_base = MPX_INVALID_BOUNDS_DIR;
>
> What's the point of initializing bd_base here. I had to look
FYI, we noticed the below changes on
commit 76835b0ebf8a7fe85beb03c75121419a7dec52f0 ("futex: Ensure
get_futex_key_refs() always implies a barrier")
0429fbc0bdc297d6 76835b0ebf8a7fe85beb03c751 testbox/testcase/testparams
-- --
1 - 100 of 280 matches
Mail list logo
