Naoya Horiguchi writes:
> On Fri, Dec 07, 2012 at 11:06:41AM +0530, Aneesh Kumar K.V wrote:
> ...
>> > From: Naoya Horiguchi
>> > Date: Thu, 6 Dec 2012 20:54:30 -0500
>> > Subject: [PATCH v2] HWPOISON, hugetlbfs: fix warning on freeing hwpoisoned
>> > hugepage
>> >
>> > This patch fixes the war
On Fri, Dec 07, 2012 at 03:35:15PM +0800, Xishi Qiu wrote:
> Hi Borislav, you mean we should move this to the beginning of
> soft_offline_page()?
>
> soft_offline_page()
> {
> ...
> get_any_page()
> ...
> /*
>* Synchronized using the page lock with memory_failure()
On Thu, Dec 6, 2012 at 6:09 PM, Joonsoo Kim wrote:
> The purpose of iterating a vmlist is finding vm area with specific
> virtual address. find_vm_area() is provided for this purpose
> and more efficient, because it uses a rbtree.
> So change it.
You no longer take the 'vmlist_lock'. This is safe
On 2012/12/7 15:25, Borislav Petkov wrote:
> On Fri, Dec 07, 2012 at 10:53:41AM +0800, Xishi Qiu wrote:
>> On x86 platform, if we use "/sys/devices/system/memory/soft_offline_page" to
>> offline a
>> free page twice, the value of mce_bad_pages will be added twice. So this is
>> an error,
>> sinc
This patch initializes IOMMU groups based on the IOMMU
configuration discovered during the PCI scan on POWERNV
(POWER non virtualized) platform. The IOMMU groups are
to be used later by VFIO driver (PCI pass through).
It also implements an API for mapping/unmapping pages for
guest PCI drivers and
If an application has an expensive function implemented with a large
tree of calls to helper functions, the default call-graph presentation
will be dominated by the many different call-chains within that
function. By treating the function as a black box, we can collect the
call-chains leading into
VFIO implements platform independent stuff such as
a PCI driver, BAR access (via read/write on a file descriptor
or direct mapping when possible) and IRQ signaling.
The platform dependent part includes IOMMU initialization
and handling. This patch implements an IOMMU driver for VFIO
which does map
On Fri, Dec 07, 2012 at 10:53:41AM +0800, Xishi Qiu wrote:
> On x86 platform, if we use "/sys/devices/system/memory/soft_offline_page" to
> offline a
> free page twice, the value of mce_bad_pages will be added twice. So this is
> an error,
> since the page was already marked HWPoison, we should s
Hi,
> -Original Message-
> From: Sergei Shtylyov [mailto:sshtyl...@mvista.com]
> Sent: 2012年12月7日 2:16
> To: Yang, Wenyou
> Cc: linux-arm-ker...@lists.infradead.org; linux-watch...@vger.kernel.org;
> Lin, JM;
> Ferre, Nicolas; linux-kernel@vger.kernel.org; w...@iguana.be;
> plagn...@jcros
On Sat, Nov 3, 2012 at 9:39 PM, Yinghai Lu wrote:
> For root bus hot add, fw could assign some resource for the devices for
> that root bus before notifying os via acpi, we should check and use those
> resources at first just like we do for booting path.
>
> At first, we need to refactor x86 pci p
On 15:53 Tue 04 Dec , Wenyou Yang wrote:
> From: Jean-Christophe PLAGNIOL-VILLARD
>
> The atmel_spi use only gpio for chip select.
no this patch need go on the TOP of mine
that is plan for 3.8
Best Regards,
J.
>
> Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD
> [wenyou.y...@atmel.com: A
On 2012/12/7 14:43, Tang Chen wrote:
> On 11/27/2012 06:00 PM, Wen Congyang wrote:
>> For hot removing memory, we sholud remove page table about the memory.
>> So the patch searches a page table about the removed memory, and clear
>> page table.
>
> (snip)
>
>> +void __meminit
>> +kernel_physica
On Thu, Dec 6, 2012 at 2:42 PM, Mark Langsdorf
wrote:
> Highbank processors depend on the external ECME to perform voltage
> management based on a requested frequency. Communication between the
> A9 cores and the ECME happens over the pl320 IPC channel.
>
> Signed-off-by: Mark Langsdorf
> Reviewe
On 12/06/2012 09:00 PM, Michael S. Tsirkin wrote:
> On Sun, Dec 02, 2012 at 09:33:53AM +0800, Asias He wrote:
>> diff --git a/drivers/vhost/Kconfig.blk b/drivers/vhost/Kconfig.blk
>> new file mode 100644
>> index 000..ff8ab76
>> --- /dev/null
>> +++ b/drivers/vhost/Kconfig.blk
>> @@ -0,0 +1,10
Hi there,
I'm wondering this is a typo in Documentation/kernel-parameters.txt
about "kernelcore=":
In the event, a node is too small to have both
kernelcore and Movable pages, kernelcore pages will
take priority and other nodes will have a larger number
of kernelcore page
Hi Guenter,
On Friday 07 December 2012 10:49:47 Guenter Roeck wrote:
> My own idea for a solution was to keep integer based handles, but replace
> gpio_desc[] with a hash table. But ultimately I don't really care how
> it is done.
>
> Do you have a solution for gpiochip_find_base() in mind, and h
On 17:37 Thu 06 Dec , ludovic.desroches wrote:
> Hi,
>
> On 12/04/2012 08:53 AM, Wenyou Yang wrote:
> >From: Richard Genoud
> >
> >Signed-off-by: Richard Genoud
> >[wenyou.y...@atmel.com: add spi nodes for other atmel SOC]
> >Signed-off-by: Wenyou Yang
> >Cc: li...@arm.linux.org.uk
> >---
>
On Wed, Dec 5, 2012 at 7:12 PM, Yinghai Lu wrote:
> On Wed, Dec 5, 2012 at 5:57 PM, H. Peter Anvin wrote:
>> Hi Eric,
>>
>> Could you give a list of struct boot_params field which are initialized
>> properly by kexec? I think we need to do the sentinel hack, and want to
>> know what to whitelist
On Thu, Dec 6, 2012 at 10:25 PM, Myron Stowe wrote:
> The "ACPI Hot Plug PCI Controller ("acpiphp")" sub-driver may be compiled
> as a module. Kernel modules are instantiated somewhat randomly - the
> order in which they are linked as the kernel as built - thus if there are
> any dependencies on
Hi Greg,
> > Yes, I've received an email saying that the patch will show up in the next
> > release of the linux-next tree, but I was not aware that linux-next tree
> > means 3.8-rc1.
>
> It does not, you didn't read the next sentance which described when the
> patch would be sent to Linus...
Th
On 11/27/2012 06:00 PM, Wen Congyang wrote:
For hot removing memory, we sholud remove page table about the memory.
So the patch searches a page table about the removed memory, and clear
page table.
(snip)
+void __meminit
+kernel_physical_mapping_remove(unsigned long start, unsigned long end)
Hi Andrew,
Today's linux-next merge of the akpm tree got a conflict in mm/vmscan.c
between commit c702418f8a2f ("mm: vmscan: do not keep kswapd looping
forever due to individual uncompactable zones") from Linus' tree and
commit "mm: use IS_ENABLED(CONFIG_COMPACTION) instead of
COMPACTION_BUILD" fr
The "ACPI Hot Plug PCI Controller Driver ("acpiphp")" can be either
statically built-in or a kernel module. If statically built-in, the
sub-driver needs to remain registered and in place in order to accommodate
any future hot-plug insertion events of devices it supports.
As currently implemented,
The external declarations trigger warnings from ./scripts/checkpatch.pl
such as:
WARNING: space prohibited between function name and open parenthesis '('
#32: FILE: drivers/pci/hotplug/acpiphp.h:194:
+extern void acpiphp_glue_init (void);
This patch removes the extraneous spaces between the
ioc->diag_trigger_mpi is an SL_WH_MPI_TRIGGERS_T struct.
There is a cut and paste error here and SL_WH_EVENT_TRIGGERS_T is used
instead of SL_WH_MPI_TRIGGERS_T. Since the SL_WH_EVENT_TRIGGERS_T is
smaller than SL_WH_MPI_TRIGGERS_T, it means we only clear part of the
buffer.
Signed-off-by: Dan Ca
The "ACPI Hot Plug PCI Controller ("acpiphp")" sub-driver may be compiled
as a module. Kernel modules are instantiated somewhat randomly - the
order in which they are linked as the kernel as built - thus if there are
any dependencies on the ordering of attaching sub-drivers, they can not be
effect
acpiphp_glue_init() always returns 0. This patch changes the return
type from an 'int' to 'void'.
No functional change.
Signed-off-by: Myron Stowe
---
drivers/pci/hotplug/acpiphp.h |2 +-
drivers/pci/hotplug/acpiphp_core.c |4 +++-
drivers/pci/hotplug/acpiphp_glue.c |4 +---
Both sub-drivers of the "PCI Root Bridge ("pci_bridge")" driver, "acpiphp"
and "pci_slot", have been converted to statically built-in functionality
added directly from within "pci_bridge".
With the conversions there are no remaining usages of the 'struct
acpi_pci_driver' list based infrastructure.
With the "ACPI PCI Slot Detection Driver ("pci_slot")" conversion in place
- being statically built-in to the kernel and no longer capable of being a
kernel module - remove the use of acpi_pci_[un]register_driver() and add
its functionality from directly within the "pci_root" driver.
Signed-off-by
This patch moves the call of dmi_check_system() from acpi_pci_slot_init()
to acpi_pci_slot_add(). This is in preparation for converting the
"pci_slot" sub-driver to being statically built into the kernel.
No functional change.
Signed-off-by: Myron Stowe
---
drivers/acpi/pci_slot.c | 57
The "ACPI PCI Slot Detection ("pci_slot")" sub-driver may be compiled as a
module. Kernel modules are instantiated somewhat randomly - the order in
which they are linked as the kernel as built - thus if there are any
dependencies on the ordering of attaching sub-drivers, they can not be
effectivel
During early boot, the kernel performs ACPI enumeration in which host
bridges are discovered (subsys_initcall(acpi_pci_root_init)). Later
drivers, both built-in and modules such as the "ACPI PCI Slot Detection
Driver ("pci_slot")", are loaded (module_init(acpi_pci_slot_init)) thus we
end up with t
acpiphp_add_bridge() always returns 0. This patch changes the return
type from an 'int' to 'void'.
No functional change.
Signed-off-by: Myron Stowe
---
drivers/pci/hotplug/acpiphp_glue.c |8 +++-
include/linux/pci-acpi.h |4 ++--
2 files changed, 5 insertions(+), 7 delet
With the "ACPI Hot Plug PCI Controller Driver ("acpiphp")" conversion in
place - being statically built-in to the kernel and no longer capable of
being a kernel module - remove the use of acpi_pci_[un]register_driver()
and add its functionality from directly within the "pci_root" driver.
Signed-of
This patch collapses the initialization call chain of "acpiphp" by calling
acpi_pci_[un]register_driver() directly within acpiphp_{init,exit}(),
removing the intervening acpiphp_glue_{init,exit}() call.
No functional change.
Signed-off-by: Myron Stowe
---
drivers/pci/hotplug/acpiphp.h |
This patch renames, and changes to external function types, add_bridge()
and remove_bridge() so that they can used directly as the add and remove
interfaces of "acpiphp".
No functional change.
Signed-off-by: Myron Stowe
---
drivers/pci/hotplug/acpiphp.h |3 +++
drivers/pci/hotplug/acp
This patch collapses the initialization call chain of "acpiphp" by calling
acpiphp_glue_init() directly within acphphp_init(), removing the
intervening init_acpi() call.
No functional change.
Signed-off-by: Myron Stowe
---
drivers/pci/hotplug/acpiphp_core.c | 24 +++-
1 f
From: Yinghai Lu
It causes confusion.
We may only need acpi hp for pci host bridge.
Split host bridge hot-add support to pci_root_hp, and keep acpiphp simple.
-v2: put back pci_root_hp change in one patch
-v3: add pcibios_resource_survey_bus() calling
-v4: remove not needed code with remove_br
The "PCI Root Bridge ("pci_root")" driver includes support for attaching
sub-drivers. acpi_pci_register_driver() and acpi_pci_unregister_driver()
are the interfaces that sub-drivers use to attach themselves.
Currently there are only two callers of acpi_pci_register_driver(): the
"ACPI Hot Plug PC
On Thu, Dec 06, 2012 at 08:24:11AM +0800, Axel Lin wrote:
> Signed-off-by: Axel Lin
Applied, thanks.,
--
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
We should return NULL on failure instead of returning a freed pointer.
Signed-off-by: Dan Carpenter
diff --git a/drivers/block/aoe/aoedev.c b/drivers/block/aoe/aoedev.c
index e66ccbf..98f2965 100644
--- a/drivers/block/aoe/aoedev.c
+++ b/drivers/block/aoe/aoedev.c
@@ -461,6 +461,7 @@ aoedev_by_a
On Fri, Dec 07, 2012 at 11:06:41AM +0530, Aneesh Kumar K.V wrote:
...
> > From: Naoya Horiguchi
> > Date: Thu, 6 Dec 2012 20:54:30 -0500
> > Subject: [PATCH v2] HWPOISON, hugetlbfs: fix warning on freeing hwpoisoned
> > hugepage
> >
> > This patch fixes the warning from __list_del_entry() which i
Michal Marek writes:
> It looks good, but looking at your patch, I just noticed that we have two
> versions of the SYMBOL_PREFIX macro in the kernel now:
>
> scripts/Makefile.lib has had since some time
>
> ifdef CONFIG_SYMBOL_PREFIX
> _sym_flags = -DSYMBOL_PREFIX=$(patsubst "%",%,$(CONFIG_SYMBOL_
On Fri, Dec 7, 2012 at 9:05 AM, Tim Gardner wrote:
> On 12/06/2012 03:46 PM, Dave Airlie wrote:
>
>>>
>>> ttm_page_pool_init_locked(&_manager->wc_pool, GFP_HIGHUSER,
>>> "wc");
>>>
>>> @@ -817,6 +821,7 @@ int ttm_page_alloc_init(struct ttm_mem_global *glob,
>>> unsigned max_pages)
>>>
On 2012-12-7 10:57, Toshi Kani wrote:
> On Fri, 2012-12-07 at 00:40 +0800, Jiang Liu wrote:
>> On 12/04/2012 08:10 AM, Toshi Kani wrote:
>>> On Mon, 2012-12-03 at 12:25 +0800, Hanjun Guo wrote:
On 2012/11/30 6:27, Toshi Kani wrote:
> On Thu, 2012-11-29 at 12:48 +0800, Hanjun Guo wrote:
>>>
On Thu, Dec 06, 2012 at 06:20:24PM -0800, Andrew Morton wrote:
> On Thu, 6 Dec 2012 21:03:44 -0500 Naoya Horiguchi
> wrote:
>
> > This patch fixes the warning from __list_del_entry() which is triggered
> > when a process tries to do free_huge_page() for a hwpoisoned hugepage.
> >
> > ChangeLog
This removes the sparse warning:
arch/x86/kernel/crash.c:49:32: sparse: incompatible types in comparison
expression (different address spaces)
Reported-by: kbuild test robot
Signed-off-by: Zhang Yanfei
---
arch/x86/include/asm/kexec.h |4 +++-
arch/x86/kernel/crash.c |4 ++--
2 fi
Naoya Horiguchi writes:
> On Thu, Dec 06, 2012 at 02:36:52PM -0800, Andrew Morton wrote:
>> On Wed, 5 Dec 2012 16:47:36 -0500
>> Naoya Horiguchi wrote:
>>
>> > This patch fixes the warning from __list_del_entry() which is triggered
>> > when a process tries to do free_huge_page() for a hwpoiso
On Fri, Dec 07, 2012 at 09:47:57AM +0800, Axel Lin wrote:
> To clear the mask bit, setting data argument to be 0 with proper mask setting
> for lp8788_update_bits. We don't need the var array here.
Applied, thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the b
On Fri, Dec 07, 2012 at 04:01:10AM +, Alexandra Chin wrote:
> Hi Greg,
>
> > That is because they were new features, and not regressions, so they
> > will be showing up in Linus's tree for 3.8-rc1.
> >
> > > May I know status of this patch? Please let me know if there is anything I
> > > shou
> To clear the mask bit, setting data argument to be 0 with proper mask
> setting
> for lp8788_update_bits. We don't need the var array here.
>
> Signed-off-by: Axel Lin
Thanks!
Acked-by: Milo(Woogyom) Kim
N�r��yb�X��ǧv�^�){.n�+{zX����ܨ}���Ơz�&j:+v���zZ+��+zf���h���~
Sorry, dropped the CCs when I replied... I don't normally use the
Gmail web interface :)
On Thu, Dec 6, 2012 at 7:59 PM, Greg Kroah-Hartman
wrote:
> 3.6-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Calvin Walton
>
> commit a51d4ed01e5bb
Hi Greg,
> That is because they were new features, and not regressions, so they
> will be showing up in Linus's tree for 3.8-rc1.
>
> > May I know status of this patch? Please let me know if there is anything I
> > should do.
>
> Didn't you get an email when I applied the patches saying where th
On Thu, Dec 06, 2012 at 11:35:47PM +, Grant Likely wrote:
> Fix problem discovered with sparse:
> + drivers/spi/spi.c:1554:37: sparse: incompatible types in comparison
> expression (different signedness)
> drivers/spi/spi.c: In function 'spi_write_then_read':
> drivers/spi/spi.c:1554:23: warni
On Thu, Dec 6, 2012 at 7:39 PM, Ying Han wrote:
> On Mon, Nov 26, 2012 at 10:47 AM, Michal Hocko wrote:
>> mem_cgroup_iter curently relies on css->id when walking down a group
>> hierarchy tree. This is really awkward because the tree walk depends on
>> the groups creation ordering. The only guar
On Fri, Dec 7, 2012 at 8:09 AM, Wedson Almeida Filho wrote:
> I don't have the setup anymore, I'll give it a shot if I ever get back it
> back.
>
> I have a question though: why do we need to get a reference to the
> parent? If the assumption is that the callee can release its reference
Because
On Thu, Dec 06, 2012 at 02:04:27PM +, Grant Likely wrote:
> Alright, applied. I've also merged in your spi-next tree. Let me know if
> that causes problems because it needs to be rebased.
No problem - do you just want to take over the SPI tree again or should
I carry on applying things?
--
To
On Mon, Nov 26, 2012 at 10:47 AM, Michal Hocko wrote:
> mem_cgroup_iter curently relies on css->id when walking down a group
> hierarchy tree. This is really awkward because the tree walk depends on
> the groups creation ordering. The only guarantee is that a parent node
> is visited before its ch
Hi Joonsoo,
On Fri, Dec 7, 2012 at 12:09 AM, Joonsoo Kim wrote:
> This patchset remove vm_struct list management after initializing vmalloc.
> Adding and removing an entry to vmlist is linear time complexity, so
> it is inefficient. If we maintain this list, overall time complexity of
> adding an
From: Cong Ding
Date: Fri, 7 Dec 2012 00:15:47 +
> On Fri, Dec 07, 2012 at 12:06:44AM +, Cong Ding wrote:
>> the variables zero and unres_qlen_max are only used when CONFIG_SYSCTL is
>> defined, otherwise it causes the following sparse warning when we turn on
>> CONFIG_SYSCTL.
> sorry for
Hi Samuel,
Today's linux-next merge of the mfd tree got a conflict in
drivers/mmc/host/Kconfig between commit 3a96dff0f828 ("mmc: SD/MMC Host
Controller for Wondermedia WM8505/WM8650") from the mmc tree and commit
ff984e57d36e ("mmc: Add realtek pcie sdmmc host driver") from the mfd
tree.
I fixed
On 2012-12-06, H. Peter Anvin wrote:
> On 12/05/2012 11:56 PM, Woody Wu wrote:
>> Hi, list
>>
>> Does anyone here familiar to the serial 8250 driver?
>>
>> I enabled two uart ports in my board definition, but the ports doesn't
>> appear after I loaded the kernel (3.4.19). I discovered, it failed
On Fri, Dec 07, 2012 at 02:16:28AM +0100, Ingo Molnar wrote:
>
> * Christoph Hellwig wrote:
>
> > No, the problem is that the thing is not just a) wrong, but b)
> > only made it in through sneaky ways.
>
> People disagree with a), and b) only really matters if a) is
> true.
Wow.
Let me para
On Fri, 2012-12-07 at 00:40 +0800, Jiang Liu wrote:
> On 12/04/2012 08:10 AM, Toshi Kani wrote:
> > On Mon, 2012-12-03 at 12:25 +0800, Hanjun Guo wrote:
> >> On 2012/11/30 6:27, Toshi Kani wrote:
> >>> On Thu, 2012-11-29 at 12:48 +0800, Hanjun Guo wrote:
> On 2012/11/29 2:41, Toshi Kani wrote:
Hi
It should be fixed in 3.7-rc8
Mikulas
On Sat, 1 Dec 2012, Sasha Levin wrote:
> Hi all,
>
> While fuzzing with trinity inside a KVM tools guest, running latest -next,
> I've
> stumbled on:
>
> [ 3130.099477] ==
> [ 3130.104862] [ INFO: p
On x86 platform, if we use "/sys/devices/system/memory/soft_offline_page" to
offline a
free page twice, the value of mce_bad_pages will be added twice. So this is an
error,
since the page was already marked HWPoison, we should skip the page and don't
add the
value of mce_bad_pages.
$ cat /proc/
On Thu, 2012-12-06 at 16:19 -0800, Andrew Morton wrote:
> On Thu, 06 Dec 2012 15:37:30 -0800
> Joe Perches wrote:
> > Can you please pick this up for -next now and I'll
> > redo my patches against -next for -rc1 so I'm not
> > delayed until 3.9?
>
> It would be better to do things in the other or
On Thu, Dec 06, 2012 at 04:45:18PM +0900, Alexandre Courbot wrote:
> With the current API, GPIOs are manipulated through an integer which
> represents their unique number across the system. This poses problems in
> terms of portability, scalability and flexibility: for instance, the
> number of val
Hi Jens,
Today's linux-next merge of the block tree got a conflict in
block/blk-exec.c between commit 893d290f1d74 ("block: Don't access
request after it might be freed") from Linus' tree and commit
c246e80d8673 ("block: Avoid that request_fn is invoked on a dead queue")
from the block tree.
I fi
On Fri, Dec 07, 2012 at 02:08:37AM +0100, Ingo Molnar wrote:
>
> * Martin Steigerwald wrote:
>
> > > The thing that people are complaining about is exactly the
> > > reverse of this. It's *protecting* us from making mistakes,
> > > and doesn't actually add any new interfaces in itself.
> > >
>
On Thu, 2012-12-06 at 18:09 +0100, Sylvain Munaut wrote:
> The "%5lu" part of the sprintf only guarantees a minimum length,
> not a maximum one. This patch should make it correct for any
> possible timestamp.
>
> This problem dates back from the printk conversion to records AFAICT.
>
> I've teste
On Fri, 2012-12-07 at 00:47 +0800, Jiang Liu wrote:
> On 12/05/2012 07:23 AM, Toshi Kani wrote:
> > On Tue, 2012-12-04 at 17:16 +0800, Hanjun Guo wrote:
> >> On 2012/12/4 8:10, Toshi Kani wrote:
> >>> On Mon, 2012-12-03 at 12:25 +0800, Hanjun Guo wrote:
> On 2012/11/30 6:27, Toshi Kani wrote:
On Fri, 07 Dec 2012 at 00:06 GMT, Cong Ding wrote:
> the variables zero and unres_qlen_max are only used when CONFIG_SYSCTL is
> defined, otherwise it causes the following sparse warning when we turn on
> CONFIG_SYSCTL.
>
commit b93196dc5af7729ff7cc50d3d322ab1a364aa14f
Author: Cong Wang
Date:
Hi Tang,
On 2012/12/7 9:42, Tang Chen wrote:
> Hi Wu,
>
> I met some problems when I was digging into the code. It's very
> kind of you if you could help me with that. :)
>
> If I misunderstood your code, please tell me.
> Please see below. :)
>
> On 12/03/2012 10:23 AM, Jianguo Wu wrote:
>> S
On Thu, 6 Dec 2012 21:03:44 -0500 Naoya Horiguchi
wrote:
> This patch fixes the warning from __list_del_entry() which is triggered
> when a process tries to do free_huge_page() for a hwpoisoned hugepage.
>
> ChangeLog v2:
> - simply use list_del_init instead of introducing new hugepage list
>
On Wed, Dec 05, 2012 at 10:13:42PM +, Luck, Tony wrote:
> > This patch fixes the warning from __list_del_entry() which is triggered
> > when a process tries to do free_huge_page() for a hwpoisoned hugepage.
>
> Ultimately it would be nice to avoid poisoning huge pages. Generally we know
> the
>
> The treatment of a burst wake-up however is a little more interesting.
> There are two reasonable trains of thought one can follow, the first
> is that:
> - If it IS truly bursty you don't really want it factoring into long
> term averages since steady state is not going to include that task;
Hello Greg Kroah-Hartman:
于 2012年12月04日 01:13, Paul Fulghum 写道:
> Fix call to line discipline receive_buf by synclink drivers.
> Dummy flag buffer argument is ignored by N_HDLC line discipline but might
> be of insufficient size if accessed by a different line discipline
> selected by mistake. fl
On Thu, 6 Dec 2012 20:22:42 -0500 Naoya Horiguchi
wrote:
> > --- a/mm/rmap.c~hwpoison-hugetlbfs-fix-rss-counter-warning-fix
> > +++ a/mm/rmap.c
> > @@ -1249,14 +1249,14 @@ int try_to_unmap_one(struct page *page,
> > update_hiwater_rss(mm);
> >
> > if (PageHWPoison(page) && !(flags &
This driver, submitted on behalf of Cypress Semiconductor Corporation and
additional contributors, provides support for the Cypress PS/2 Trackpad.
Note that the patch "increase struct ps2dev cmdbuf[] to 8 bytes" [5] is a
PREREQUISITE for this patch.
This [PATCH v6] version differs from my previou
On Thu, 2012-12-06 at 00:08 -0800, Dmitry Torokhov wrote:
> [...]
Hi Dmitry-
Thanks again for your review. The forthcoming PATCH v6 addresses all of
your requests, except for:
> > + __set_bit(INPUT_PROP_BUTTONPAD, input->propbit);
>
> I do not think it should be marked INPUT_PROP_BUTTONPAD
Hi, Steven,
(2012/11/30 23:17), Steven Rostedt wrote:
[snip]
>
> Actually, I would have:
>
> status\input | 0 | 1 |else|
> --++++
> not allocated |(do nothing)| alloc+swap | EINVAL |
> --++-
Hi John,
Today's linux-next merge of the wireless-next tree got a conflict in
include/linux/bcma/bcma_driver_chipcommon.h between commits ef85fb28305f
("bcma: add locking around GPIO register accesses") and cf0936b06d8e
("bcma: add GPIO driver") from the mips tree and commits a22a3114a820
("bcma:
On Thursday 06 December 2012 22:42:59 Grant Likely wrote:
> how about "gpio_chip_hwnum()" to somewhat match irqdomain convention?
Sure, matching existing interfaces is better. "git grep hwnum" does not seem
to reveal much related to irqdomain though?
> I've only lightly scanned this patch, but I
On Thu, Dec 06, 2012 at 02:36:52PM -0800, Andrew Morton wrote:
> On Wed, 5 Dec 2012 16:47:36 -0500
> Naoya Horiguchi wrote:
>
> > This patch fixes the warning from __list_del_entry() which is triggered
> > when a process tries to do free_huge_page() for a hwpoisoned hugepage.
> >
> > Originally
This patch adds capability in vxlan to identify received
checksummed inner packets and signal them to the upper layers of
the stack. The driver needs to set the skb->encapsulation bit
and also set the skb->ip_summed to CHECKSUM_UNNECESSARY.
Signed-off-by: Joseph Gasparakis
---
drivers/net/vxlan.
On Thu, Dec 06, 2012 at 11:50:24AM -0500, Theodore Ts'o wrote:
> On Thu, Dec 06, 2012 at 07:06:45AM -0500, Christoph Hellwig wrote:
> >
> > Also the only conference outcome I remember is that everyone at LSF
> > except for Ted basically said "no fucking way".
> >
>
> At LSF, that's correct. And
This patch adds support in the kernel for offloading in the NIC Tx and Rx
checksumming for encapsulated packets (such as VXLAN and IP GRE).
Signed-off-by: Joseph Gasparakis
Signed-off-by: Peter P Waskiewicz Jr
Signed-off-by: Alexander Duyck
---
include/linux/ip.h|5 ++
include/linu
Allow VXLAN to make use of Tx checksum offloading and Tx scatter-gather.
The advantage to these two changes is that it also allows the VXLAN to
make use of GSO.
Signed-off-by: Joseph Gasparakis
Signed-off-by: Peter P Waskiewicz Jr
Signed-off-by: Alexander Duyck
---
drivers/net/vxlan.c | 10 +
From: Alexander Duyck
This change allows the VXLAN to enable Tx checksum offloading even on
devices that do not support encapsulated checksum offloads. The
advantage to this is that it allows for the lower device to change due
to routing table changes without impacting features on the VXLAN itsel
This patch allows ixgbe to recognize encapsulated packets and do the tx
checksum offload in hardware. This patch is only for demonstration
purposes and should not be applied.
Signed-off-by: Joseph Gasparakis
Signed-off-by: Alexander Duyck
---
drivers/net/ethernet/intel/ixgbe/ixgbe_main.c | 46
The series contains updates to add in the NIC Rx and Tx checksumming support
for encapsulated packets.
The sk_buff needs to somehow have information of the inner packet, and adding
three fields for the inner mac, network and transport headers was the prefered
approach.
Not adding these fields wo
To clear the mask bit, setting data argument to be 0 with proper mask setting
for lp8788_update_bits. We don't need the var array here.
Signed-off-by: Axel Lin
---
drivers/regulator/lp8788-ldo.c | 11 +--
1 file changed, 1 insertion(+), 10 deletions(-)
diff --git a/drivers/regulator/l
Hi Wu,
I met some problems when I was digging into the code. It's very
kind of you if you could help me with that. :)
If I misunderstood your code, please tell me.
Please see below. :)
On 12/03/2012 10:23 AM, Jianguo Wu wrote:
Signed-off-by: Jianguo Wu
Signed-off-by: Jiang Liu
---
include/li
On Thu, 2012-12-06 at 17:36 -0200, Herton Ronaldo Krzesinski wrote:
> On Mon, Dec 03, 2012 at 02:31:52PM +, Ben Hutchings wrote:
> > 3.2-stable review patch. If anyone has any objections, please let me know.
> >
> > --
> >
> > From: Tejun Heo
> >
> > commit 201e72acb2d3821e
On Thu, 6 Dec 2012, Omar Ramirez Luna wrote:
> I was planning to wait until linux-omap had the changes from iommu
> tree (probably at rc1), if the merge conflict resulted in
> arch/arm/mach-omap2/cclock44xx_data.c still having ipu and dsp clocks,
> in this case the hwmod data changes wouldn't be n
Hi Paul,
On Thu, Dec 6, 2012 at 6:59 PM, Paul Walmsley wrote:
> Hi Omar,
>
> On Thu, 6 Dec 2012, Omar Ramirez Luna wrote:
>
>> I have checked next-20121206, it's OK to delete that file as the patch
>> from Paul is doing that for common clock framework migration; now
Hi Ludovic,
> -Original Message-
> From: Desroches, Ludovic
> Sent: 2012年12月7日 0:37
> To: Yang, Wenyou
> Cc: linux-arm-ker...@lists.infradead.org; li...@arm.linux.org.uk;
> richard.gen...@gmail.com; Lin, JM; Ferre, Nicolas;
> linux-kernel@vger.kernel.org;
> plagn...@jcrosoft.com; Desroche
On 12/07/2012 08:56 AM, Frederic Weisbecker wrote:
> 2012/12/3 Alex Shi :
>> There is 4 situations in the function:
>> 1, no task allowed group;
>> so min_load = ULONG_MAX, this_load = 0, idlest = NULL
>> 2, only local group task allowed;
>> so min_load = ULONG_MAX, this_load assign
On 12/07/2012 09:02 AM, Frederic Weisbecker wrote:
> 2012/12/7 Alex Shi :
>> On 12/07/2012 01:50 AM, Frederic Weisbecker wrote:
>>> 2012/12/3 Alex Shi :
It is impossible to miss a task allowed cpu in a eligible group.
And since find_idlest_group only return a different group which
>>
1 - 100 of 608 matches
Mail list logo