Ville et al,
It looks like commit e3ea8fa6beaf55fee64bf816f3b8a80ad733b2c2 (or
another commit in 3.13.7) broke modes which require DVI-D dual-link,
eg 2560x1440 with my panel.
I don't see these modelines in 3.13.7 or later (eg 3.14):
[ 5.582] (II) intel(0): Modeline "2560x1440"x60.0 312.25
Hello Minchan,
Nice work. It seems I forgot to reply your mail in the first RFC version
of the patch, so I just review this new one.
On 04/07/2014 10:51 AM, Minchan Kim wrote:
> Linux doesn't have an ability to free pages lazy while other OS
> already have been supported that named by
On Mon, Apr 7, 2014 at 3:25 PM, Tony Luck wrote:
> c) If not this ... then what? Separate routine to convert large numbers
>of jiffies to usec/nsecs? Should we make the existing one barf when
>handed a number that overflows?
Having thought about this a bit more - I'm leaning towards
On 8 April 2014 10:09, Chen Gang wrote:
> OK, I will/should try within this week, thanks.
Rafael has already applied this patch and has mentioned stable in
'Cc:' field. And it looks it will be applied automatically and you don't
need to do anything now :)
commit
On 8 April 2014 09:29, Jet Chen wrote:
> (Sorry for previous bad format email)
> Your patch on my testing branch in LKP system:
> git://bee.sh.intel.com/git/tchen37/linux.git timer_debug3 got the below
> dmesg.
> FYI, I applied your patch on the top of commit
>
Hi,
Thierry Reding wrote:
> On Wed, Apr 02, 2014 at 07:53:50AM +0200, Sascha Hauer wrote:
> > On Fri, Mar 28, 2014 at 09:48:58AM +0100, Lothar Waßmann wrote:
> [...]
> > > @@ -183,8 +173,11 @@ static void of_pwmchip_add(struct pwm_chip *chip)
> > > return;
> > >
> > > if
On 5 April 2014 17:33, Viresh Kumar wrote:
> kernel/time/clocksource.c | 64
> +++
> 1 file changed, 53 insertions(+), 11 deletions(-)
>
> diff --git a/kernel/time/clocksource.c b/kernel/time/clocksource.c
> index ba3e502..8054fb1 100644
> ---
On 04/08/2014 11:20 AM, 管雪涛 wrote:
> I'd like to put the code into asm/io.h, and make it static.
>
It sounds OK to me, but I don't know why the other architectures (e.g.
arm, powerpc, x86) put them into ".c".
iomem_is_exclusive() and page_is_ram() are all extern functions, so for
me,
On Mon, 2014-04-07 at 15:18 -0400, David Miller wrote:
> And in the loopback case, it is the decnet stack's responsibility to
> make sure ->dn_ptr is setup properly, else it should fail the module
> load and stack initialization.
> can fix this properly.
This was based on Sasha report and my
When building the name for the workqueue thread, make sure a format
string cannot leak in from the disk name.
Signed-off-by: Kees Cook
---
drivers/mtd/ubi/block.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/mtd/ubi/block.c b/drivers/mtd/ubi/block.c
index
On 04/08/2014 12:08 PM, Viresh Kumar wrote:
> On 8 April 2014 06:31, Chen Gang wrote:
>>> @stable: please apply this for v3.14, as it broke in that cycle..
>
> This wouldn't work..
>
>> Thank you.
>
> Can you please send it again for stable as well? Add my Ack in the patch
> and follow what's
Hi Rob,
On Friday 04 April 2014 03:47 AM, Rob Herring wrote:
> From: Rob Herring
>
> Unify the various architectures __dtb_start and __dtb_end definitions
> moving them into of_fdt.h.
>
> Signed-off-by: Rob Herring
> Cc: Vineet Gupta
> Cc: James Hogan
> Cc: Ralf Baechle
> Cc: Jonas Bonn
>
On 7 April 2014 22:45, Sören Brinkmann wrote:
> I see this on 3.13 too (in our vendor tree, but I think mainline would
> show the behavior as well). It probably worth to add it into the 3.13
> stable kernel.
Thanks.. Patch sent for stable tree.
--
To unsubscribe from this list: send the line
On 8 April 2014 06:31, Chen Gang wrote:
>> @stable: please apply this for v3.14, as it broke in that cycle..
This wouldn't work..
> Thank you.
Can you please send it again for stable as well? Add my Ack in the patch
and follow what's mentioned here:
Documentation/stable_kernel_rules.txt
--
To
On Mon, Apr 7, 2014 at 2:25 PM, Mel Gorman wrote:
> On Mon, Apr 07, 2014 at 12:42:40PM -0700, H. Peter Anvin wrote:
>> On 04/07/2014 12:36 PM, Cyrill Gorcunov wrote:
>> > On Mon, Apr 07, 2014 at 12:27:10PM -0700, H. Peter Anvin wrote:
>> >> On 04/07/2014 11:28 AM, Mel Gorman wrote:
>> >>>
>> >>>
On 04/07/2014 08:31 PM, Matthew Garrett wrote:
On Mon, Apr 07, 2014 at 08:21:00PM -0700, Guenter Roeck wrote:
On 04/07/2014 07:48 PM, Matthew Garrett wrote:
You shouldn't need to install an SCI handler - the way the hardware will
generate an SCI is to raise a GPE. If you know which GPE the
Hi Rob,
On Fri, Apr 4, 2014 at 2:16 AM, Rob Herring wrote:
> From: Rob Herring
>
> With libfdt support, we can take advantage of helper accessors in libfdt
> for accessing the FDT header data. This makes the code more readable and
> makes the FDT blob structure more opaque to the kernel. This
Hi all,
Please do not add material intended for v3.16 to your linux-next included
branches until after v3.15-rc1 is released.
This tree still fails (more than usual) the powerpc allyesconfig build.
Changes since 20140407:
Dropped trees: akpm-current, akpm (too complex conflicts)
The powerpc
On 04/07/2014 09:32 PM, Kevin Easton wrote:
> On Wed, Apr 02, 2014 at 10:40:16AM -0700, John Stultz wrote:
>> On Wed, Apr 2, 2014 at 9:36 AM, Johannes Weiner wrote:
>>> I'm just dying to hear a "normal" use case then. :)
>> So the more "normal" use cause would be marking objects volatile and
>>
On Wed, Apr 02, 2014 at 10:40:16AM -0700, John Stultz wrote:
> On Wed, Apr 2, 2014 at 9:36 AM, Johannes Weiner wrote:
> > I'm just dying to hear a "normal" use case then. :)
>
> So the more "normal" use cause would be marking objects volatile and
> then non-volatile w/o accessing them
On Mon, Apr 07, 2014 at 08:21:00PM -0700, Guenter Roeck wrote:
> On 04/07/2014 07:48 PM, Matthew Garrett wrote:
> >You shouldn't need to install an SCI handler - the way the hardware will
> >generate an SCI is to raise a GPE. If you know which GPE the device
> >raises (my recollection is that for
On 04/07/2014 07:48 PM, Matthew Garrett wrote:
On Fri, Apr 04, 2014 at 09:25:50AM -0700, Guenter Roeck wrote:
Is there a clean way to use any of those to implement interrupt support
for this driver ? I thought about hijacking the SCI interrupt by registering
an interrupt handler with
I'd like to put the code into asm/io.h, and make it static.
> +#ifdef CONFIG_STRICT_DEVMEM
> +/*
> + * devmem_is_allowed() checks to see if /dev/mem access to a certain
> + * address is valid. The argument is a physical page number.
> + * We mimic x86 here by disallowing access to system RAM as
Since v1:
Edited the comment according to Srivatsa's suggestion.
During the testing, we encounter below WARN followed by Oops:
WARNING: at kernel/sched/core.c:6218
...
NIP [c0101660] .build_sched_domains+0x11d0/0x1200
LR [c0101358]
This introduces CONFIG_DEBUG_RODATA, making kernel text and rodata
read-only. Additionally, this splits rodata from text so that rodata can
also be NX, which may lead to wasted memory when aligning to SECTION_SIZE.
The read-only areas are made writable during ftrace updates. Additional
work is
Adds CONFIG_ARM_KERNMEM_PERMS to separate the kernel memory regions
into section-sized areas that can have different permisions. Performs
the NX permission changes during free_initmem, so that init memory can be
reclaimed.
This uses section size instead of PMD size to reduce memory lost to
This implements CONFIG_DEBUG_RODATA, along with ftrace support. It is
intended to be used on top of Rabin Vincent's patch "arm: ftrace: work
with CONFIG_DEBUG_SET_MODULE_RONX", so that ftrace will work with both
config options.
Thanks!
-Kees
--
To unsubscribe from this list: send the line
Thanks,
Acked-by: Xuetao Guan
- Chen Gang 写道：
> Need use 'clk' instead of 'mclk', which is the original removed local
> variable.
>
> The related original commit:
>
> "652ed95 cpufreq: introduce cpufreq_generic_get() routine"
>
> The related error with allmodconfig for unicore32:
>
>
From: xiao jin
Date: Tue, 25 Mar 2014 15:54:36 +0800
Subject: [PATCH] cdc-acm: some enhancement on acm delayed write
We find two problems on acm tty write delayed mechanism.
(1) When acm resume, the delayed wb will be started. But now
only one write can be saved during acm suspend. More acm
On 04/07/2014 03:14 PM, KOSAKI Motohiro wrote:
>>> This change hwpoison and migration tag number. maybe ok, maybe not.
>> Though depending on config can't these tag numbers change anyway?
> I don't think distro disable any of these.
Well, it still shouldn't break if the config options are turned
On 6 April 2014 18:28, Paul Bolle wrote:
> On Fri, 2014-04-04 at 10:47 -0700, Mike Turquette wrote:
>> Haojian Zhuang (3):
>> [...]
>> clk: hip04: add clock driver
>
> This clock driver is only built if CONFIG_ARCH_HIP04 is set. But I
> couldn't find a Kconfig symbol ARCH_HIP04. (I
Hi Benjamin,
> Fengguang,
>
> I ran your script against freshly-checked-out source from staging-next, and
> was not able to reproduce the error with it. My boot log is attached. I
> noticed that your log did not have "Hypervisor detected: KVM" in the trace.
> The KVM options in your script
On Mon, Apr 7, 2014 at 3:00 PM, Sebastian Reichel wrote:
> On Mon, Apr 07, 2014 at 11:38:01AM -0500, Rob Herring wrote:
>> On Sat, Apr 5, 2014 at 5:26 PM, Sebastian Reichel wrote:
>> > Add common DT binding documentation for touchscreen devices and
>> > implement
Although, I am not comfortable discussing the content of my mail on the
Internet owing to lots of unsolicited/Spam
mails on the net nowadays. The fact is I have made up my mind to will my late
Husband's funds to you so you can
use it for charity duties and good work to humanity in your
On 04/04/2014 10:44 PM, Stephen Chandler Paul wrote:
> Like many other Windows 8 laptops the ThinkPad Helix's backlight has a
> broken ACPI interface and can only be properly adjusted by using the
> video card's native backlight control. This adds the ThinkPad Helix to
> the list of laptops
On Fri, Apr 04, 2014 at 09:25:50AM -0700, Guenter Roeck wrote:
> Is there a clean way to use any of those to implement interrupt support
> for this driver ? I thought about hijacking the SCI interrupt by registering
> an interrupt handler with acpi_install_sci_handler(), but that would restrict
>
On 04/04/2014 02:35 AM, Greg Kurz wrote:
> The current kernel code assumes big endian and parses RTAS events all
> wrong. The most visible effect is that we cannot honor EPOW events,
> meaning, for example, we cannot shut down a guest properly from the
> hypervisor.
>
> This new patch is largely
Hi, Srivatsa
It's nice to have you confirmed the fix, and thanks for the well-writing
comments, will apply them and send out the new patch later :)
Regards,
Michael Wang
On 04/07/2014 06:15 PM, Srivatsa S. Bhat wrote:
> Hi Michael,
>
> On 04/02/2014 08:59 AM, Michael wang wrote:
>> During the
On 2014-4-7 20:21, Rafael J. Wysocki wrote:
> On Thursday, April 03, 2014 08:37:30 PM Hanjun Guo wrote:
>> The UEFI Forum included the ACPI spec in its portfolio in October 2013
>> and will host future spec iterations, following the ACPI v5.0a release.
>>
>> A UEFI Forum working group named ACPI
On Mon, Mar 31, 2014 at 9:24 PM, Naoya Horiguchi
wrote:
> The information about "pfn-node" mapping seldom (or never) changes after boot,
> so it seems better to me that adding a new interface somewhere under
> /sys/devices/system/node/nodeN which shows pfn range of a given node.
> If this doesn't
(2014/04/03 3:08), Luiz Capitulino wrote:
> Next commit will add new code which will want to call the
> for_each_node_mask_to_alloc() macro. Move it, its buddy
> for_each_node_mask_to_free() and their dependencies up in the file so
> the new code can use them. This is just code movement, no logic
The following patches are intended for inclusion in the 3.15 kernel.
They include a number of bug fixes, some cleanups, and the conversion
to pci_enable_msix_range.
Please let me know if there are any issues.
Thanks,
Jon
---
Alexander Gordeev (4):
ntb: Fix leakage of
From: Alexander Gordeev
Signed-off-by: Alexander Gordeev
Signed-off-by: Jon Mason
---
drivers/ntb/ntb_hw.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/ntb/ntb_hw.c b/drivers/ntb/ntb_hw.c
index 2774d35..0e8ae70 100644
--- a/drivers/ntb/ntb_hw.c
+++ b/drivers/ntb/ntb_hw.c
@@
From: Alexander Gordeev
This is an cleanup effort to make ntb_setup_msix() more
readable - use ntb_setup_bwd_msix() to init MSI-Xs on
BWD hardware and ntb_setup_snb_msix() - on SNB hardware.
Function ntb_setup_snb_msix() also initializes MSI-Xs the
way it should has been done - looping
(2014/04/04 22:30), Luiz Capitulino wrote:
On Fri, 4 Apr 2014 12:05:17 +0900
Yasuaki Ishimatsu wrote:
(2014/04/03 3:08), Luiz Capitulino wrote:
HugeTLB is limited to allocating hugepages whose size are less than
MAX_ORDER order. This is so because HugeTLB allocates hugepages via
the buddy
(2014/04/03 3:08), Luiz Capitulino wrote:
> Hugepages pages never get the PG_reserved bit set, so don't clear it. But
> add a warning just in case.
>
> Signed-off-by: Luiz Capitulino
> ---
Reviewed-by: Yasuaki Ishimatsu
Thanks,
Yasuaki Ishimatsu
> mm/hugetlb.c | 5 +++--
> 1 file changed,
(2014/04/03 3:08), Luiz Capitulino wrote:
> Signed-off-by: Luiz Capitulino
> ---
Reviewed-by: Yasuaki Ishimatsu
Thanks,
Yasuaki Ishimatsu
> include/linux/hugetlb.h | 5 +
> mm/hugetlb.c| 28 ++--
> 2 files changed, 19 insertions(+), 14 deletions(-)
From: Alexander Gordeev
Signed-off-by: Alexander Gordeev
Signed-off-by: Jon Mason
---
drivers/ntb/ntb_hw.c | 15 ---
drivers/ntb/ntb_hw.h | 2 --
2 files changed, 4 insertions(+), 13 deletions(-)
diff --git a/drivers/ntb/ntb_hw.c b/drivers/ntb/ntb_hw.c
index eba1ed5..06d605c
From: Roland Dreier
In the code for Xeon devices in back-to-back mode with xeon_errata_workaround
disabled, the downstream device puts the wrong value in SNB_B2B_XLAT_OFFSETL
(SNB_MBAR01_DSD_ADDR vs. SNB_MBAR01_USD_ADDR).
This was spotted while reading code, since the typo has no practical
ffs_epfile_io() is called from userspace, while ffs_func_esp_disable() might
be called from USB disconnect interrupt, the two functions would run in parallel
but they are not well protected, that epfile->ep would be removed by
ffs_func_esp_disable() during ffs_epfile_io() is referring this
...
Command line: initrd=initrd.img
inst.stage2=hd:LABEL=Fedora\x20rawhide\x20x86_64 xdriver=modesetting
BOOT_IMAGE=vmlinuz
Kernel command line: initrd=initrd.img
inst.stage2=hd:LABEL=Fedora\x20rawhide\x20x86_64 xdriver=modesetting
BOOT_IMAGE=vmlinuz
...
[ cut here ]
jiffies_to_usecs() returns an "int" so it can only handle times up to
2^32 microseconds (1 hour 11 minutes 34 seconds) before truncation
occurs. This is a problem for the "uptime" trace clock added in
commit 8aacf017b065a805d27467843490c976835eb4a5
tracing: Add "uptime" trace clock that
On Wed, Mar 19, 2014 at 02:57:06PM +0100, Miklos Szeredi wrote:
> Hi Dave,
>
> On Mon, Feb 17, 2014 at 07:19:11PM +1100, Dave Chinner wrote:
> > On Wed, Feb 12, 2014 at 06:18:52PM +0100, Miklos Szeredi wrote:
> > > On Tue, Feb 11, 2014 at 05:01:41PM +0100, Miklos Szeredi wrote:
> > > > On Mon,
ffs_epfile_io() is called from userspace, while ffs_func_esp_disable() might
be called from USB disconnect interrupt, the two functions would run in parallel
but they are not well protected, that epfile->ep would be removed by
ffs_func_esp_disable() during ffs_epfile_io() is referring this
On 04/08/2014 06:34 AM, Mel Gorman wrote:
> pgdat->reclaim_nodes tracks if a remote node is allowed to be reclaimed by
> zone_reclaim due to its distance. As it is expected that zone_reclaim_mode
> will be rarely enabled it is unreasonable for all machines to take a penalty.
> Fortunately, the
On 04/08/2014 06:34 AM, Mel Gorman wrote:
> zone_reclaim_mode causes processes to prefer reclaiming memory from local
> node instead of spilling over to other nodes. This made sense initially when
> NUMA machines were almost exclusively HPC and the workload was partitioned
> into nodes. The NUMA
Hi,
This patch didn't apply. Please check for me.
Thanks.
Daeseok Youn
2014-03-12 2:02 GMT+09:00 Jayamohan Kallickal :
>
>
> -Original Message-
> From: Daeseok Youn [mailto:daeseok.y...@gmail.com]
> Sent: Thursday, February 20, 2014 5:13 PM
> To: jbottom...@parallels.com
> Cc: Jayamohan
On 04/07/2014 08:08 PM, Viresh Kumar wrote:
> On 7 April 2014 17:34, Chen Gang wrote:
>> Need use 'clk' instead of 'mclk', which is the original removed local
>> variable.
>>
>> The related original commit:
>>
>> "652ed95 cpufreq: introduce cpufreq_generic_get() routine"
>>
>> The related error
If list_for_each_entry exits without finding the ntb_device, the dev
pointer will not be NULL. Thus the check will never be true and the
code will not exit when it should. Correct this by adding a bool to
determine when the device is found, otherwise exit in good fashion.
Signed-off-by: Jon
Provide a better event interface between the client and transport
Signed-off-by: Jon Mason
---
drivers/net/ntb_netdev.c| 16
drivers/ntb/ntb_hw.h| 4 +---
drivers/ntb/ntb_transport.c | 1 -
include/linux/ntb.h | 5 +
4 files changed, 18 insertions(+),
From: Alexander Gordeev
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() or pci_enable_msi_exact()
and pci_enable_msix_range() or
In ntb_netdev_open, when ntb_transport_rx_enqueue fails the skb that was
attempting to be enqueued is not freed. Free this skb on the
ntb_transport_rx_enqueue error.
Signed-off-by: Jon Mason
---
drivers/net/ntb_netdev.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git
Some white space and 80 char overruns corrected.
Signed-off-by: Jon Mason
---
drivers/net/ntb_netdev.c| 2 +-
drivers/ntb/ntb_hw.c| 19 ++-
drivers/ntb/ntb_hw.h| 2 +-
drivers/ntb/ntb_transport.c | 19 +--
include/linux/ntb.h | 14
On Mon, Mar 31, 2014 at 11:53:31PM +0900, Namjae Jeon wrote:
> From: Namjae Jeon
>
> FALLOC_FL_INSERT_RANGE was mentioned as the opposite command of collapse
> range from discussion between Hugh Dickins and Dave Chinner.
>
> In continuation of the work of making the process of non linear
On Fri, Apr 4, 2014 at 8:27 AM, Jason Cooper wrote:
> Alexei,
>
> Thanks for the heads up.
>
> On Thu, Apr 03, 2014 at 03:12:38PM -0700, Alexei Starovoitov wrote:
>> It seems commit f4d4ffc03efc ("kbuild: dtbs_install: new make target")
>> breaks 'fakeroot make-kpkg' package creation on ubuntu.
On 04/04, Kumar Gala wrote:
> Add a driver for the global clock controller found on IPQ8064 based
> platforms. This should allow most non-multimedia device drivers to probe
> and control their clocks.
>
> This is currently missing clocks for SATA, USB, and networking devices.
>
> Signed-off-by:
Hi Geert,
I have a piece of hardware where the two normal serial ports are
inaccessible and buried inside the system somewhere. I put a PCIe
serial port card in which is normally detected as a ST16650V2:
[ 17.939057] :13:00.0: ttyS2 at I/O 0x1008 (irq = 18, base_baud =
115200) is a
unsubscribe linux-kernel
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
--
On Sun, Mar 30, 2014 10:31 PM BST Larry Finger wrote:
>On 03/28/2014 03:26 PM, Alexey Khoroshilov wrote:
> If allocation of io_dmabuf fails, rtl8187_probe() calls usb_put_dev(udev)
> while usb_get_dev(udev) is not called yet. As a result refcnt is decremented
>
On Fri, Mar 14, 2014 at 03:34:18PM +, Liviu Dudau wrote:
> Use the generic host bridge functions to provide support for
> PCI Express on arm64. There is no support for ISA memory.
>
> Signed-off-by: Liviu Dudau
> Tested-by: Tanmay Inamdar
> ---
> arch/arm64/Kconfig| 19 +++-
>
On Thu, Feb 6, 2014 at 9:28 AM, Ivan T. Ivanov wrote:
> + spi8_default: spi8_default {
> + mosi {
> + pins = "gpio45";
> + function = "blsp_spi8";
> +
(2014/04/07 16:05), Namhyung Kim wrote:
> The dwarf_getcfi() only checks .debug_frame section for CFI, but as
> most binaries only have .eh_frame it'd return NULL and it makes
> some variables inaccessible.
>
> Using dwarf_getcfi_elf (along with dwarf_getelf()) allows to show and
> add probe to
On Mon, Apr 07, 2014 at 11:34:28PM +0100, Mel Gorman wrote:
> pgdat->reclaim_nodes tracks if a remote node is allowed to be reclaimed by
> zone_reclaim due to its distance. As it is expected that zone_reclaim_mode
> will be rarely enabled it is unreasonable for all machines to take a penalty.
>
On Mon, Apr 07, 2014 at 11:34:27PM +0100, Mel Gorman wrote:
> zone_reclaim_mode causes processes to prefer reclaiming memory from local
> node instead of spilling over to other nodes. This made sense initially when
> NUMA machines were almost exclusively HPC and the workload was partitioned
> into
On Mon, Apr 07, 2014 at 09:30:57PM +0200, Sebastian Andrzej Siewior wrote:
>
> You dropped that part where I suggested to use something like AES+CTR
> and create the numbers on demand and dropping that attempt to create as
> much random data with custom functions as possible. You completly
On Fri, Mar 14, 2014 at 9:34 AM, Liviu Dudau wrote:
> Some architectures do not share x86 simple view of the PCI I/O space
> and instead use a range of addresses that map to bus addresses. For
> some architectures these ranges will be expressed by OF bindings
> in a device tree file.
>
>
Greg Kurz writes:
> The current kernel code assumes big endian and parses RTAS events all
> wrong. The most visible effect is that we cannot honor EPOW events,
> meaning, for example, we cannot shut down a guest properly from the
> hypervisor.
>
> This new patch is largely inspired by Nathan's
On Mon, Apr 07, 2014 at 10:19:19PM +0200, Michal Marek wrote:
> Hi Linus,
>
> besides the kbuild branch, here is the LTO build support by Andi. It is
> a separate branch, because it depends on other patches by Andi which
> were merged through other trees. The link-time-optimization build is an
>
On Mon, 2014-04-07 at 15:09 -0700, H. Peter Anvin wrote:
> > so, it sounds like...
> >
> > 1) ACPI
> > 2) KEYBOARD
> > 3) ACPI
> > 4) KEYBOARD
> > 5) EFI
> > possibly 6) CF9
> > 7) TRIPLE *or* BIOS
> >
> > is what you would say makes sense, right? And really all there is to
> > decide is
On Mon, Apr 07, 2014 at 10:10:46PM +0200, Thomas Bächler wrote:
> Am 07.04.2014 19:46, schrieb Thomas Bächler:
> > Am 07.04.2014 19:30, schrieb Andi Kleen:
> Do you have a specific config?
> Specific compiler version?
> >>>
> >>> Using gcc 4.8 from Arch Linux with the configuration at
Hi,
On Mon, Apr 07, 2014 at 03:12:09PM -0700, Randy Dunlap wrote:
> On 04/05/2014 11:42 AM, Apelete Seketeli wrote:
> > Document the process of writing an musb glue layer by taking the
> > Ingenic JZ4740 glue layer as an example, as it seems more simple than
> > most glue layers due to the basic
In __rtc_read_alarm(), if the alarm time retrieved by
rtc_read_alarm_internal() from the device contains invalid values
(e.g. month=2,mday=31) and the year not set (=-1), the initialization
will loop infinitely because the year-fixing loop expects the
time being invalid due to leap year.
Fix
On Mon, Apr 7, 2014 at 4:07 AM, Liviu Dudau wrote:
> On Mon, Apr 07, 2014 at 10:14:18AM +0100, Benjamin Herrenschmidt wrote:
>> On Mon, 2014-04-07 at 09:46 +0100, Liviu Dudau wrote:
>> >
>> > *My* strategy is to get rid of pci_domain_nr(). I don't see why we need
>> > to have arch specific way of
On Mon, Apr 07, 2014 at 09:57:00PM +0200, Toralf Förster wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On 04/07/2014 08:59 PM, Frederic Weisbecker wrote:
> > On Mon, Apr 07, 2014 at 08:16:24PM +0200, Toralf Förster wrote:
> >> -BEGIN PGP SIGNED MESSAGE- Hash: SHA256
> >>
On Fri, Apr 04, 2014 at 03:07:13PM +0200, Stanimir Varbanov wrote:
> >> diff --git a/drivers/crypto/qce/dma.h b/drivers/crypto/qce/dma.h
> >> new file mode 100644
> >> index ..932b02fd8f25
> >> --- /dev/null
> >> +++ b/drivers/crypto/qce/dma.h
> >> @@ -0,0 +1,57 @@
> >> +/*
> >> + *
zone_reclaim_mode causes processes to prefer reclaiming memory from local
node instead of spilling over to other nodes. This made sense initially when
NUMA machines were almost exclusively HPC and the workload was partitioned
into nodes. The NUMA penalties were sufficiently high to justify
pgdat->reclaim_nodes tracks if a remote node is allowed to be reclaimed by
zone_reclaim due to its distance. As it is expected that zone_reclaim_mode
will be rarely enabled it is unreasonable for all machines to take a penalty.
Fortunately, the zone_reclaim_mode() path is already slow and it is
When it was introduced, zone_reclaim_mode made sense as NUMA distances
punished and workloads were generally partitioned to fit into a NUMA
node. NUMA machines are now common but few of the workloads are NUMA-aware
and it's routine to see major performance due to zone_reclaim_mode being
disabled
There's nothing we can do different if pci_load_and_free_saved_state()
fails, other than maybe print some log message, but the actual re-load
of the state is an unnecessary step here since we've only just saved
it. We can cleanup a coverity warning and eliminate the unnecessary
stop by freeing
When sizing the TPH capability we store the register containing the
table size into the 'dword' variable, but then use the uninitialized
'byte' variable to analyze the size. The table size is also actually
reported as an N-1 value, so correct sizing to account for this.
The round_up() for both
On 04/07/2014 06:08 PM, Bryan Wu wrote:
> On Fri, Apr 4, 2014 at 10:01 AM, Sasha Levin wrote:
>> Currently, we may attempt to unregister a trigger more than once, for
>> example when we receive two consecutive reboot notifications, or when
>> we do a regular unregistration plus reboot
Coverity reports use of a tained scalar used as a loop boundary.
For the most part, any values passed from userspace for a DMA mapping
size, IOVA, or virtual address are valid, with some alignment
constraints. The size is ultimately bound by how many pages the user
is able to lock, IOVA is tested
Overall nothing very serious here. We botch the size of a PCIe
capability due to a cut-n-paste error, but nobody has noticed due to
the rarity of the capability. A 32bit host could possibly see some
overflows attempting to do a DMA map, but all of the parameters are
also validated elsewhere, so
On 04/07, Paul Bolle wrote:
> Commit 8fc1b0f87d9f ("ARM: qcom: Split Qualcomm support into legacy and
> multiplatform") removed Kconfig symbol ARCH_MSM_DT. But that commit
> left one (optional) dependency on ARCH_MSM_DT untouched.
>
> Three Kconfig symbols used to depend on ARCH_MSM_DT:
>> This change hwpoison and migration tag number. maybe ok, maybe not.
>
> Though depending on config can't these tag numbers change anyway?
I don't think distro disable any of these.
>> I'd suggest to use younger number than hwpoison.
>> (That's why hwpoison uses younger number than migration)
On 04/05/2014 11:42 AM, Apelete Seketeli wrote:
> Document the process of writing an musb glue layer by taking the
> Ingenic JZ4740 glue layer as an example, as it seems more simple than
> most glue layers due to the basic feature set of the JZ4740 USB device
> controller.
>
> Signed-off-by:
Hi Zhang,
How is this beneficial when compared to RPS(receive packet steering)?
Can you please provide more details on what this patch does?
Thanks
Sharat
On Mon, Apr 7, 2014 at 12:42 PM, David Miller wrote:
>
> The net-next tree is not open yet, I will announce when it is and you can
>
On 04/07/2014 03:04 PM, Adam Williamson wrote:
>
> So if I'm following correctly, we should be able to sort the methods
> into three buckets:
>
> 1) known to (almost) always be 'safe'
> 2) may cause system freeze if they fail
> 3) definitely cause system freeze if they fail
>
> We put the
On Fri, Apr 4, 2014 at 10:01 AM, Sasha Levin wrote:
> Currently, we may attempt to unregister a trigger more than once, for
> example when we receive two consecutive reboot notifications, or when
> we do a regular unregistration plus reboot notification.
>
> This leads to the following error
推荐：多年的网络营销经验 帮您做出最准确的营销决策
如何打造自己的自动赚钱机器，实现睡觉赚钱？
都在使用：http://www.cloudedm.net/
联系电话：153 6363 4438
营销军火库|绿色通道|云端邮件群发
创始人：刘建
项目推荐：让7.3亿QQ知道你 2014最牛QQ营销软件系统
http://user.qzone.qq.com/506951936/blog/1393424220
至此~
1 - 100 of 966 matches
Mail list logo
