On 08/01/2012 04:30 PM, H. Peter Anvin wrote:
> On 08/01/2012 04:09 PM, Meredydd Luff wrote:
#
# x32-specific system call numbers start at 512 to avoid cache impact
>>>
>>> I think that should be common, not 64 (as should kcmp be).
>>
>> I copied the original execve, which is 64.
>>
>
Hello Borislav,
On Wed, Aug 01, 2012 at 07:38:37PM +0200, Borislav Petkov wrote:
> Hi,
>
> I'm hitting the WARN_ON in $Subject with latest linus:
> v3.5-8833-g2d534926205d on a 4-node AMD system. As it looks from
> dmesg, it is happening on node 0, 1 and 2 but not on 3. Probably the
> pgdat->nr_z
On Wed, Aug 1, 2012 at 3:08 PM, Lukas Hejtmanek wrote:
> On Wed, Aug 01, 2012 at 02:32:17PM -0700, Yinghai Lu wrote:
>> yes, i knew that.
>>
>> one patch in my for-pci-next should address that.
>>
>> http://git.kernel.org/?p=linux/kernel/git/yinghai/linux-yinghai.git;a=patch;h=fcce563f868e296f46a2
On 01/08/12 14:54, Cruz Julian Bishop wrote:
> Previously, when calling is_between(a, b, c), the calculation was wrong.
> It counted C as between A and B if C was equal to B, but not A.
>
> Example of this are:
>
> is_between(1, 10, 10) = 1 (Expected: 0)
> is_between(1, 10, 1) = 0 (Expected: 0)
>
On Wed, Aug 01, 2012 at 05:36:52PM -0500, Alexis R. Cortes wrote:
> This patch is intended to work around a known issue on the
> SN65LVPE502CP USB3.0 re-driver that can delay the negotiation
> between a device and the host past the usual handshake timeout,
Paragraphs, please. :)
> if that happe
Is it still Wednesday?
As promised, here are the last bits for md. Primarily performance
improvements made possible the new plugging code. These can make a
significant difference on SDD's and a noticeable difference on spinning rust.
Thanks,
NeilBrown
The following changes since commit 74018
That bar could be 64bit pref mem.
Signed-off-by: Yinghai Lu
Cc: David Airlie
Reviewed-by: Daniel Vetter
---
drivers/char/agp/intel-gtt.c | 14 ++
1 file changed, 10 insertions(+), 4 deletions(-)
Index: linux-2.6/drivers/char/agp/intel-gtt.c
=
Sorry misunderstood your offlist mail I can cook up an x32 binary easily
enough.
Meredydd Luff wrote:
>On 2 Aug 2012 00:33, "H. Peter Anvin" wrote:
>> > Sorry, you're right. The argument vector needs compatibility
>support.
>> >
>> > This means you need an x32 version of the function
>
>Thi
Oleg Nesterov writes:
> [...]
> Well, not sure this will help... but if you can reproduce this,
> may be you can identify the sender of the wrong SIGHUP at least.
>
> cd /sys/kernel/debug/tracing/
> echo "sig==1" >> events/signal/signal_generate/filter
> echo 1 >> options/stackt
On Sun, 13 May 2012, John David Anglin wrote:
> On 13-May-12, at 4:40 PM, John David Anglin wrote:
>
> > Yes, the revised change fixes the compilation error. I'll know in a while
> > if
> > my config boots.
>
>
> I successfully booted 3.4-rc7 with this change on rp3440 (4 cpu smp). My
> bui
This fixes two issues that could cause incompatibility between
kernel versions:
- If a tracer uses SECCOMP_RET_TRACE to select a syscall number
higher than the largest known syscall, emulate the unknown
vsyscall by returning -ENOSYS. (This is unlikely to make a
noticeable difference on
Hi Len,
After merging the acpi tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/iommu/amd_iommu_init.c: In function 'early_amd_iommu_init':
drivers/iommu/amd_iommu_init.c:1535:2: error: implicit declaration of function
'acpi_get_table_with_size' [-Werror=implicit-fu
Reviewed-by: Kenji Kaneshige
Regards,
Kenji Kaneshige
> -Original Message-
> From: Jiang Liu [mailto:liu...@gmail.com]
> Sent: Thursday, August 02, 2012 12:54 AM
> To: Bjorn Helgaas; Don Dutile
> Cc: Jiang Liu; Yinghai Lu; Izumi, Taku/泉 拓; Rafael J . Wysocki; Kaneshige,
> Kenji/金重 憲治; Y
Reviewed-by: Kenji Kaneshige
Regards,
Kenji Kaneshige
> -Original Message-
> From: Jiang Liu [mailto:liu...@gmail.com]
> Sent: Thursday, August 02, 2012 12:54 AM
> To: Bjorn Helgaas; Don Dutile
> Cc: Jiang Liu; Yinghai Lu; Izumi, Taku/泉 拓; Rafael J . Wysocki; Kaneshige,
> Kenji/金重 憲治; Y
Reviewed-by: Kenji Kaneshige
Regards,
Kenji Kaneshige
> -Original Message-
> From: Jiang Liu [mailto:liu...@gmail.com]
> Sent: Thursday, August 02, 2012 12:54 AM
> To: Bjorn Helgaas; Don Dutile
> Cc: Jiang Liu; Yinghai Lu; Izumi, Taku/泉 拓; Rafael J . Wysocki; Kaneshige,
> Kenji/金重 憲治; Y
On Tue, Jul 31, 2012 at 02:02:25PM -0400, chetan loke wrote:
> On Tue, Jul 31, 2012 at 1:27 PM, Jon Mason wrote:
> >
> > I don't see the benefit of having the driver in staging. Any vendors
> > who would notice the ntb driver in staging would be sitting on these
> > mailing lists and hopefully ha
On Tue, Jul 31, 2012 at 03:25:55PM -0700, Greg KH wrote:
> On Sun, Jul 29, 2012 at 05:26:33PM -0700, Jon Mason wrote:
> > +struct ntb_transport_qp;
> > +
> > +struct ntb_client {
> > + char *name;
> > + int (*probe) (struct pci_dev *pdev);
> > + void (*remove) (struct pci_dev *pdev);
> > +};
On Thu, 2 Aug 2012 11:20:33 +1000
Stephen Rothwell wrote:
> Hi Len,
>
> After merging the acpi tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/iommu/amd_iommu_init.c: In function 'early_amd_iommu_init':
> drivers/iommu/amd_iommu_init.c:1535:2: error: implici
show_backtrace must have an valid task when calling unwind_stack,
so fix it by checking first.
root@romashell:/root> echo l > /proc/sysrq-trigger
SysRq : Show backtrace of all active CPUs
Stack : 81bf 81ceroot@octeon:/root> 81bf
0036
ff
On Thu, Aug 2, 2012 at 5:04 AM, Ondrej Zary wrote:
> Enable autoloading of leds-clevo-mail by using MODULE_DEVICE_TABLE.
>
Thanks, applied to my for-next branch
-Bryan
> Signed-off-by: Ondrej Zary
>
> --- a/drivers/leds/leds-clevo-mail.c
> +++ b/drivers/leds/leds-clevo-mail.c
> @@ -31,7 +31,7 @
On Thu, Aug 2, 2012 at 5:04 AM, Ondrej Zary wrote:
> There are more variants of Clevo M5x0V laptops and Positivo Mobile is just
> one of them.
> Another one is UMAX VisionBook 2400WXC. Use only generic Clevo DMI strings to
> match all
> variants.
>
Thanks, applied to my for-next branch
-Bryan
Remove the non-sense isdnloop revision transform code, so as to fix:
[ 22.016214] isdnloop-ISDN-driver Rev 1.11.6.7
[ 22.097508] isdnloop: (loop0) virtual card added
[ 22.174400] Kernel panic - not syncing: stack-protector: Kernel stack is
corrupted in: 83244972
[ 22.174400]
[
On Wed, Aug 01, 2012 at 04:21:47PM -0700, Greg KH wrote:
> On Wed, Aug 01, 2012 at 05:54:00PM +0100, Matthew Garrett wrote:
> > On Tue, Jul 31, 2012 at 03:32:40PM -0700, Greg KH wrote:
> >
> > > With this series, does the latest MacBook work properly for the Intel
> > > graphics driver? Or is thi
Hi all,
After merging the final tree, today's linux-next build (sparc64 defconfig)
produced this warning:
mm/shmem.c: In function 'shmem_interleave':
mm/shmem.c:1343:9: warning: assignment makes integer from pointer without a
cast [enabled by default]
Introduced by commit c3cfa3129c03 ("tmpfs:
Hi all,
Please do not add anything to linux-next included branches/series that is
destined for v3.7 until after v3.6-rc1 is released.
Reminder: do not rebase your branches before asking Linus to pull them ...
Changes since 20120731:
Removed trees: samsung, bjdooks-i2c (unfetchable)
Linus' tree
On Wed, Aug 1, 2012 at 8:31 PM, Fan Du wrote:
> show_backtrace must have an valid task when calling unwind_stack,
> so fix it by checking first.
[...]
> --- a/arch/mips/kernel/traps.c
> +++ b/arch/mips/kernel/traps.c
> @@ -151,6 +151,10 @@ static void show_backtrace(struct task_struct *task,
> co
On 12-07-31 04:21 PM, Randy Dunlap wrote:
> On 07/31/2012 11:58 AM, Salar Ali Mumtaz wrote:
>
>> Now the debug_info only shows y/n/m values.
>>
>
>
> or no value at all??
Yes.
y/n/m or no value at all.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of
On 2012年08月02日 12:18, Kevin Cernekee wrote:
On Wed, Aug 1, 2012 at 8:31 PM, Fan Du wrote:
show_backtrace must have an valid task when calling unwind_stack,
so fix it by checking first.
[...]
--- a/arch/mips/kernel/traps.c
+++ b/arch/mips/kernel/traps.c
@@ -151,6 +151,10 @@ static void show_
> -Original Message-
> From: Ira W. Snyder [mailto:i...@ovro.caltech.edu]
> Sent: Thursday, August 02, 2012 12:36 AM
> To: Liu Qiang-B32616
> Cc: linux-cry...@vger.kernel.org; linuxppc-...@lists.ozlabs.org; linux-
> ker...@vger.kernel.org; dan.j.willi...@gmail.com; Vinod Koul;
> herb...@gon
> -Original Message-
> From: Ira W. Snyder [mailto:i...@ovro.caltech.edu]
> Sent: Thursday, August 02, 2012 12:31 AM
> To: Liu Qiang-B32616
> Cc: linux-cry...@vger.kernel.org; linuxppc-...@lists.ozlabs.org; linux-
> ker...@vger.kernel.org; dan.j.willi...@gmail.com; Vinod Koul;
> herb...@gon
> -Original Message-
> From: Ira W. Snyder [mailto:i...@ovro.caltech.edu]
> Sent: Thursday, August 02, 2012 1:31 AM
> To: Liu Qiang-B32616
> Cc: linux-cry...@vger.kernel.org; linuxppc-...@lists.ozlabs.org; linux-
> ker...@vger.kernel.org; dan.j.willi...@gmail.com; Vinod Koul; Tabi Timur-
>
On Wed, Aug 01, 2012 at 03:43:37PM +0200, Oleg Nesterov wrote:
...
> However, I am not sure we can trust it. We are in kernel mode,
> DEBUGCTLMSR_BTF can be cleared by kprobes (Ananth, please correct me).
> I think we need to check TIF_BLOCKSTEP.
Kprobes resets DEBUGCTLMSR_BTF only if we have to
> -Original Message-
> From: Matthias Kaehlcke [mailto:matthias.l...@kaehlcke.net]
> Sent: Thursday, August 02, 2012 1:48 AM
> To: Venu Byravarasu
> Cc: a.zu...@towertech.it; sa...@linux.intel.com;
> broo...@opensource.wolfsonmicro.com; Laxman Dewangan;
> kyle.ma...@fuel7.com; sb...@codeaur
On Wed, 1 Aug 2012 16:59:39 -0400
Don Dutile wrote:
> On 08/01/2012 02:37 AM, Feng Tang wrote:
> > This is a preparation for removing the acpi_get_table_with_size(), as this
> > function could be well covered by acpi_get_table(), and there is no need
> > to have both of them to exist.
> >
> > v2:
This is a preparation for removing the acpi_get_table_with_size(), as this
function could be well covered by acpi_get_table(), and there is no need
to have both of them to exist.
v2: As reminded by Yinghai, apply the replacment to
drivers/iommu/amd_iommu_init.c
which is a new user of the acpi_get
Hello Chanho Min,
On 2012-08-02 오전 11:50, Chanho Min wrote:
-Original Message-
From: Kyungsik Lee [mailto:kyungsik@lge.com]
Sent: Wednesday, August 01, 2012 10:06 AM
To: Chris Ball
Cc: Venkatraman S; Jaehoon Chung; raphael.andy@gmail.com; linux-
m...@vger.kernel.org; linux-kerne
On Wed, Aug 1, 2012 at 8:00 PM, Christoph Lameter wrote:
> On Wed, 1 Aug 2012, Michael Kerrisk wrote:
>
>> Is the patch below acceptable? (I've attached the complete page as well.)
>
> Yes looks good.
Thanks for checking it!
>> See you in San Diego (?),
>
> Yup. I will be there too.
See you the
On Wed, Aug 01, 2012 at 11:20:13AM -0600, Stephen Warren wrote:
> On 08/01/2012 09:54 AM, Jiang Liu wrote:
> > From: Jiang Liu
> >
> > Use PCIe capabilities access functions to simplify PCIe ARM implementation.
> >
> > Signed-off-by: Jiang Liu
>
> This is probably fine from my perspective assu
A) Introduction:
This patchset adds MOVABLE-dedicated node and online_movable for
memory-management.
It is used for anti-fragmentation(hugepage, big-order allocation...),
hot-removal-of-memory(virtualization, power-conserve, move memory between
systems
to make better utilities of memori
N_HIGH_MEMORY stands for the nodes that has normal or high memory.
N_MEMORY stands for the nodes that has any memory.
The code here need to handle with the nodes which have memory, we should
use N_MEMORY instead.
Signed-off-by: Lai Jiangshan
---
fs/proc/kcore.c|2 +-
fs/proc/task_mmu.c
N_HIGH_MEMORY stands for the nodes that has normal or high memory.
N_MEMORY stands for the nodes that has any memory.
The code here need to handle with the nodes which have memory, we should
use N_MEMORY instead.
Signed-off-by: Lai Jiangshan
---
mm/mempolicy.c | 12 ++--
1 files chang
N_HIGH_MEMORY stands for the nodes that has normal or high memory.
N_MEMORY stands for the nodes that has any memory.
The code here need to handle with the nodes which have memory, we should
use N_MEMORY instead.
Signed-off-by: Lai Jiangshan
---
mm/vmstat.c |4 ++--
1 files changed, 2 inser
SLUB only fucus on the nodes which has normal memory, so ignore the other
node's hot-adding and hot-removing.
Signed-off-by: Lai Jiangshan
---
mm/slub.c |6 ++
1 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/mm/slub.c b/mm/slub.c
index 8c691fa..4c5bdc0 100644
--- a/mm/slub
All are prepared, we can actually introduce N_MEMORY.
add CONFIG_MOVABLE_NODE make we can use it for movable-dedicated node
Signed-off-by: Lai Jiangshan
---
drivers/base/node.c |6 ++
include/linux/nodemask.h |4
mm/Kconfig |8
mm/page_alloc.c
From: Yasuaki Ishimatsu
Setting kernelcore_max_pfn means all memory which is bigger than
the boot parameter is allocated as ZONE_MOVABLE. So memory which
is allocated by memblock also should be limited by the parameter.
The patch limits memory from memblock.
Signed-off-by: Yasuaki Ishimatsu
Si
From: Yasuaki Ishimatsu
memblock.current_limit is set directly though memblock_set_current_limit()
is prepared. So fix it.
Signed-off-by: Yasuaki Ishimatsu
Signed-off-by: Lai Jiangshan
---
arch/x86/kernel/setup.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch
When a memoryblock/memorysection is onlined by "online_movable", the kernel
will not have directly reference to the page of the memoryblock,
thus we can remove that memory any time when needed.
It makes things easy when we dynamic hot-add/remove memory, make better
utilities of memories, and helps
Fix some typos in kernel/trace.
Signed-off-by: Wang Tianhong
diff --git a/kernel/trace/ring_buffer.c b/kernel/trace/ring_buffer.c
index 49491fa..b32ed0e 100644
--- a/kernel/trace/ring_buffer.c
+++ b/kernel/trace/ring_buffer.c
@@ -2816,7 +2816,7 @@ EXPORT_SYMBOL_GPL(ring_buffer_record_enable);
From: Yasuaki Ishimatsu
memblock_find_in_range_node() does not compare memblock.current_limit
with end variable. Thus even if memblock.current_limit is smaller than
end variable, the function allocates memory address that is bigger than
memblock.current_limit.
The patch adds the check to "memblo
N_HIGH_MEMORY stands for the nodes that has normal or high memory.
N_MEMORY stands for the nodes that has any memory.
The code here need to handle with the nodes which have memory, we should
use N_MEMORY instead.
Signed-off-by: Lai Jiangshan
---
Documentation/cgroups/cpusets.txt |2 +-
incl
N_HIGH_MEMORY stands for the nodes that has normal or high memory.
N_MEMORY stands for the nodes that has any memory.
The code here need to handle with the nodes which have memory, we should
use N_MEMORY instead.
Signed-off-by: Lai Jiangshan
---
mm/vmscan.c |4 ++--
1 files changed, 2 inser
N_HIGH_MEMORY stands for the nodes that has normal or high memory.
N_MEMORY stands for the nodes that has any memory.
The code here need to handle with the nodes which have memory, we should
use N_MEMORY instead.
Signed-off-by: Lai Jiangshan
---
init/main.c |2 +-
1 files changed, 1 inserti
Currently memory_hotplug only manages the node_states[N_HIGH_MEMORY],
it forgot to manage node_states[N_NORMAL_MEMORY]. fix it.
Signed-off-by: Lai Jiangshan
---
Documentation/memory-hotplug.txt |2 +-
mm/memory_hotplug.c | 23 +--
2 files changed, 22 insert
A)==
Currently, memory-page-map(struct page array) is not defined in struct zone.
It is defined in several ways:
FLATMEM: global memmap, can be allocated from any zone <= ZONE_NORMAL
CONFIG_DISCONTIGMEM: node-specific memmap, can be allocated from any
zone <= ZONE_NORMAL w
From: Yasuaki Ishimatsu
If system can create movable node which all memory of the
node is allocated as ZONE_MOVABLE, setup_node_data() cannot
allocate memory for the node's pg_data_t.
So when memblock_alloc_nid() fails, setup_node_data() retries
memblock_alloc().
Signed-off-by: Yasuaki Ishimatsu
Current ZONE_MOVABLE (kernelcore=) setting policy with boot option doesn't meet
our requirement. We need something like kernelcore_max_addr=XX boot option
to limit the kernelcore upper address.
The memory with higher address will be migratable(movable) and they
are easier to be offline(always read
N_HIGH_MEMORY stands for the nodes that has normal or high memory.
N_MEMORY stands for the nodes that has any memory.
The code here need to handle with the nodes which have memory, we should
use N_MEMORY instead.
Since we introduced N_MEMORY, we update the initialization of node_states.
Signed-o
N_HIGH_MEMORY stands for the nodes that has normal or high memory.
N_MEMORY stands for the nodes that has any memory.
The code here need to handle with the nodes which have memory, we should
use N_MEMORY instead.
Signed-off-by: Lai Jiangshan
---
kernel/kthread.c |2 +-
1 files changed, 1 in
N_HIGH_MEMORY stands for the nodes that has normal or high memory.
N_MEMORY stands for the nodes that has any memory.
The code here need to handle with the nodes which have memory, we should
use N_MEMORY instead.
Signed-off-by: Lai Jiangshan
---
drivers/base/node.c |2 +-
mm/hugetlb.c
> -Original Message-
> From: Mark Brown [mailto:broo...@opensource.wolfsonmicro.com]
> Sent: den 1 augusti 2012 15:20
> To: Lee Jones
> Cc: linux-arm-ker...@lists.infradead.org; linux-kernel@vger.kernel.org;
> stericsson_nomadik_li...@list.st.com; linus.wall...@stericsson.com;
> a...@arndb.
N_HIGH_MEMORY stands for the nodes that has normal or high memory.
N_MEMORY stands for the nodes that has any memory.
The code here need to handle with the nodes which have memory, we should
use N_MEMORY instead.
Signed-off-by: Lai Jiangshan
---
mm/memcontrol.c | 18 +-
mm/pa
N_HIGH_MEMORY stands for the nodes that has normal or high memory.
N_MEMORY stands for the nodes that has any memory.
The code here need to handle with the nodes which have memory, we should
use N_MEMORY instead.
Signed-off-by: Lai Jiangshan
---
mm/migrate.c |2 +-
1 files changed, 1 insert
Hi Linus,
The following changes since commit bd0a521e88aa7a06ae7aabaed7ae196ed4ad867a:
Linux 3.5-rc6 (2012-07-07 17:23:56 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tyhicks/ecryptfs.git
tags/ecryptfs-3.6-rc1-fixes
for you to fetch changes
N_HIGH_MEMORY stands for the nodes that has normal or high memory.
N_MEMORY stands for the nodes that has any memory.
The code here need to handle with the nodes which have memory, we should
use N_MEMORY instead.
Signed-off-by: Lai Jiangshan
---
mm/oom_kill.c |2 +-
1 files changed, 1 inser
We have N_NORMAL_MEMORY for standing for the nodes that have normal memory with
zone_type <= ZONE_NORMAL.
And we have N_HIGH_MEMORY for standing for the nodes that have normal or high
memory.
But we don't have any word to stand for the nodes that have *any* memory.
And we have N_CPU but without
On 08/01/2012 09:20 PM, Salar Ali Mumtaz wrote:
> On 12-07-31 04:21 PM, Randy Dunlap wrote:
>> On 07/31/2012 11:58 AM, Salar Ali Mumtaz wrote:
>>
>>> Now the debug_info only shows y/n/m values.
>>>
>>
>>
>> or no value at all??
>
>
> Yes.
>
> y/n/m or no value at all.
>
so in:
Kernel suppor
On Tue, Jul 31, 2012 at 05:03:05PM -0500, Rob Herring wrote:
> For nr-gpios, I think it is typically not needed. Generally, you will
> know how many gpio lines the h/w has based on the compatible string. If
> this part really is the same part but different packages with different
> numbers of gpio,
Hi folks,
This version added REQ_FLUSH and REQ_FUA support as suggested by Christoph and
rebased against latest linus's tree.
Jens, could you please consider picking up the dependencies 1/4 and 2/4 in your
tree. Thanks!
This patchset implements bio-based IO path for virito-blk to improve
perfo
Split the mapping code in blk_rq_map_sg() to a helper
__blk_segment_map_sg(), so that other mapping function, e.g.
blk_bio_map_sg(), can share the code.
Cc: Rusty Russell
Cc: Jens Axboe
Cc: Christoph Hellwig
Cc: Tejun Heo
Cc: Shaohua Li
Cc: "Michael S. Tsirkin"
Cc: k...@vger.kernel.org
Cc: l
Add a helper to map a bio to a scatterlist, modelled after
blk_rq_map_sg.
This helper is useful for any driver that wants to create
a scatterlist from its ->make_request_fn method.
Changes in v2:
- Use __blk_segment_map_sg to avoid duplicated code
- Add cocbook style function comment
Cc: Rusty
This patch introduces bio-based IO path for virtio-blk.
Compared to request-based IO path, bio-based IO path uses driver
provided ->make_request_fn() method to bypasses the IO scheduler. It
handles the bio to device directly without allocating a request in block
layer. This reduces the IO path in
We need to support both REQ_FLUSH and REQ_FUA for bio based path since
it does not get the sequencing of REQ_FUA into REQ_FLUSH that request
based drivers can request.
REQ_FLUSH is emulated by:
1. Send VIRTIO_BLK_T_FLUSH to device
2. Wait until the flush is finished
REQ_FUA is emulated by:
1. Sen
On 07/30/2012 09:44 PM, Christoph Hellwig wrote:
On Mon, Jul 30, 2012 at 09:31:06AM +0200, Paolo Bonzini wrote:
You only need to add REQ_FLUSH support. The virtio-blk protocol does
not support REQ_FUA, because there's no easy way to do it in userspace.
A bio-based driver needs to handle both
On Thu, Aug 02, 2012 at 02:25:56PM +0800, Asias He wrote:
> We need to support both REQ_FLUSH and REQ_FUA for bio based path since
> it does not get the sequencing of REQ_FUA into REQ_FLUSH that request
> based drivers can request.
>
> REQ_FLUSH is emulated by:
> 1. Send VIRTIO_BLK_T_FLUSH to devi
On Sun, 2012-07-08 at 19:30 +0200, Joel Reardon wrote:
> This patch adds the key state map to keymap, a structure that holds the state
> of all keys in the KSA. The states are defined in an enum, and a get/set
> accessor is added. These accessors are static only: the external interface
> will simpl
Hi, Lucas, sorry for so long a delay because I have a holiday for one month.
I found Loongson-3 must turn on SWIOTLB if the system memory has
addresses above 4G. As I know, there are two ways to get a DMA addr,
the first way is use dma_alloc_coherent(), and the other one is use
map_page()/map_sg()
In case of USB bulk transfer, when himem page
is received, the usb_sg_init function sets the
urb transfer buffer to NULL. When such URB
transfer is handled, kernel crashes in PIO mode.
Handle this by mapping the highmem buffer in PIO mode.
Signed-off-by: Virupax Sadashivpetimath
---
drivers/usb
On 08/02/2012 02:27 PM, Christoph Hellwig wrote:
On Thu, Aug 02, 2012 at 02:25:56PM +0800, Asias He wrote:
We need to support both REQ_FLUSH and REQ_FUA for bio based path since
it does not get the sequencing of REQ_FUA into REQ_FLUSH that request
based drivers can request.
REQ_FLUSH is emulate
The following changes since commit 2d534926205db9ffce4bbbde67cb9b2cee4b835c:
Merge tag 'irqdomain-for-linus' of git://git.secretlab.ca/git/linux-2.6
(2012-07-31 20:44:03 -0700)
are available in the git repository at:
git://github.com/pmundt/linux-sh tags/sh-for-linus
for you to fetch chan
When I/O APIC support was converted to the generic IRQ domain code,
various things were broken. First, the number of interrupts required for
an I/O APIC can be dynamically obtained from the mp_ioapic_gsi structure
instead of hardcoded to 32. Furthermore, the legacy IRQ domain requires
the irq_domai
On Wed, Aug 01, 2012 at 04:30:22PM -0700, H. Peter Anvin wrote:
> On 08/01/2012 04:09 PM, Meredydd Luff wrote:
> >>> #
> >>> # x32-specific system call numbers start at 512 to avoid cache impact
> >>
> >> I think that should be common, not 64 (as should kcmp be).
> >
> > I copied the original ex
401 - 481 of 481 matches
Mail list logo
