Hi,
Resending the patch after a while.
Jonathan, developer of CERT Triage Tools, expressed the need
to have this information, CCing him.
But before looking at the attached patch, we need a ruling.
In the last review it was proposed to maybe generate
this information in the form of ASCII text,
It's actually more complicated than that. Old kernel images started
misbehaving from around 2.6.35-rc5 and any kernel older than that was
OK. When I recompiled the older kernels with squeeze gcc (migh have been
lenny gcc before, or different answers to make oldconfig), anything from
On Wednesday 11 July 2012, Tomoya MORINAGA wrote:
Currently, when a user wants to change UART clock,
needs to modify this source code by hand.
This patch enables changing UART clock by specifying UART clock
as module parameter.
Signed-off-by: Tomoya MORINAGA tomoya.r...@gmail.com
This
On 07/11/2012 01:18 PM, Jan Kiszka wrote:
On 2012-07-11 11:53, Avi Kivity wrote:
On 07/03/2012 10:21 PM, Alex Williamson wrote:
Here's the latest iteration of adding an interface to assert and
de-assert level interrupts from external drivers like vfio. These
apply on top of the previous
Hi,
here is finally a new version of this patch-set. Changes to the previous
version include:
* Rebased to v3.5-rc6
* Added missing Acked-by's
The potential issue with type-safety still exists. But since people are
desperatly waiting for the functionality of this patch-set I
From: Hiroshi DOYU hd...@nvidia.com
Implement the attribute for the Tegra IOMMU drivers.
Signed-off-by: Hiroshi DOYU hd...@nvidia.com
Signed-off-by: Joerg Roedel joerg.roe...@amd.com
---
drivers/iommu/tegra-gart.c |5 +
drivers/iommu/tegra-smmu.c |5 +
2 files changed, 10
Implement the attribute for the OMAP IOMMU driver.
Signed-off-by: Joerg Roedel joerg.roe...@amd.com
---
drivers/iommu/omap-iommu.c |4
1 file changed, 4 insertions(+)
diff --git a/drivers/iommu/omap-iommu.c b/drivers/iommu/omap-iommu.c
index e70ee2b..d0b1234 100644
---
Implement the attribute for the Samsung Exynos IOMMU driver.
Signed-off-by: Joerg Roedel joerg.roe...@amd.com
---
drivers/iommu/exynos-iommu.c |4
1 file changed, 4 insertions(+)
diff --git a/drivers/iommu/exynos-iommu.c b/drivers/iommu/exynos-iommu.c
index 9a114b9..5c40937 100644
---
This patch introduces an extension to the iommu-api to get
and set attributes for an iommu_domain. Two functions are
introduced for this:
* iommu_domain_get_attr()
* iommu_domain_set_attr()
These functions will be used to make the iommu-api suitable
for GART-like IOMMUs and to
Implement the attribute itself and add the code for the
AMD IOMMU driver.
Signed-off-by: Joerg Roedel joerg.roe...@amd.com
---
drivers/iommu/amd_iommu.c |4
drivers/iommu/iommu.c | 19 ---
include/linux/iommu.h |8
3 files changed, 28
Implement the attribute for the Intel IOMMU driver.
Signed-off-by: Joerg Roedel joerg.roe...@amd.com
---
drivers/iommu/intel-iommu.c |4
1 file changed, 4 insertions(+)
diff --git a/drivers/iommu/intel-iommu.c b/drivers/iommu/intel-iommu.c
index b12af2f..6cb0791 100644
---
Hi Rusty,
On Wed, Jul 11, 2012 at 06:26:49AM +0100, Rusty Russell wrote:
On Tue, 10 Jul 2012 16:52:18 +, Arnd Bergmann a...@arndb.de wrote:
On Tuesday 10 July 2012, Alan Cox wrote:
In the AArch32 kernel port many implementation decisions newer
architectures were made in a way that
On 07/11/2012 02:23 PM, Avi Kivity wrote:
On 07/09/2012 09:20 AM, Raghavendra K T wrote:
Signed-off-by: Raghavendra K Traghavendra...@linux.vnet.ibm.com
Noting pause loop exited vcpu helps in filtering right candidate to yield.
Yielding to same vcpu may result in more wastage of cpu.
On Tue, 2012-07-10 at 18:43 -0400, John Stultz wrote:
Over the weekend, Thomas got a chance to review the leap second fix
in more detail and had a few additional changes he wanted to make
to improve performance as well as style.
So this iteration includes his modifications.
Once merged,
Implement the attribute for the MSM IOMMU driver.
Acked-by: David Brown dav...@codeaurora.org
Signed-off-by: Joerg Roedel joerg.roe...@amd.com
---
drivers/iommu/msm_iommu.c |5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/iommu/msm_iommu.c b/drivers/iommu/msm_iommu.c
index
On 07/11/2012 01:17 PM, Christian Borntraeger wrote:
On 11/07/12 11:06, Avi Kivity wrote:
[...]
Almost all s390 kernels use diag9c (directed yield to a given guest cpu)
for spinlocks, though.
Perhaps x86 should copy this.
See arch/s390/lib/spinlock.c
The basic idea is using several
On Wed, Jul 11, 2012 at 5:09 AM, Ram Pai linux...@us.ibm.com wrote:
Wait.. I am not sure this will fix the problem entirely. The above check
will handle the case where the range requested is entirey out of the
root's range. But if the requested range overlapps that of the root
range, we
On 11.07.2012, at 13:04, Avi Kivity wrote:
On 07/11/2012 01:17 PM, Christian Borntraeger wrote:
On 11/07/12 11:06, Avi Kivity wrote:
[...]
Almost all s390 kernels use diag9c (directed yield to a given guest cpu)
for spinlocks, though.
Perhaps x86 should copy this.
See
* John Stultz johns...@us.ibm.com wrote:
Over the weekend, Thomas got a chance to review the leap
second fix in more detail and had a few additional changes he
wanted to make to improve performance as well as style.
So this iteration includes his modifications.
Yep, looks much saner now
On 07/11/2012 01:52 PM, Raghavendra K T wrote:
On 07/11/2012 02:23 PM, Avi Kivity wrote:
On 07/09/2012 09:20 AM, Raghavendra K T wrote:
Signed-off-by: Raghavendra K Traghavendra...@linux.vnet.ibm.com
Noting pause loop exited vcpu helps in filtering right candidate to
yield.
Yielding to same
On 11/07/12 13:04, Avi Kivity wrote:
On 07/11/2012 01:17 PM, Christian Borntraeger wrote:
On 11/07/12 11:06, Avi Kivity wrote:
[...]
Almost all s390 kernels use diag9c (directed yield to a given guest cpu)
for spinlocks, though.
Perhaps x86 should copy this.
See arch/s390/lib/spinlock.c
Hi Dmitry,
On Wed, Jul 11, 2012 at 3:15 PM, Poddar, Sourav sourav.pod...@ti.com wrote:
Hi Dmitry,
On Tue, Jul 10, 2012 at 11:43 AM, Dmitry Torokhov
dmitry.torok...@gmail.com wrote:
Hi Sourav,
On Fri, Jun 08, 2012 at 04:22:59PM +0530, Sourav Poddar wrote:
Update the Documentation with
Hi Masatake,
On Wed, Jul 11, 2012 at 01:58:31PM +0900, Masatake YAMATO wrote:
(The patch sets are rebased to bluetooth-next. Unnecessary white
spaces are trimmed.)
lsof command can tell the type of socket processes are using.
Internal lsof uses inode numbers on socket fs to resolve the type
On 2012-07-11 12:49, Avi Kivity wrote:
On 07/11/2012 01:18 PM, Jan Kiszka wrote:
On 2012-07-11 11:53, Avi Kivity wrote:
On 07/03/2012 10:21 PM, Alex Williamson wrote:
Here's the latest iteration of adding an interface to assert and
de-assert level interrupts from external drivers like vfio.
On 07/11/2012 02:16 PM, Alexander Graf wrote:
yes the data structure itself seems based on the algorithm
and not on arch specific things. That should work. If we move that to
common
code then s390 will use that scheme automatically for the cases were we
call
kvm_vcpu_on_spin(). All
What if they add 64-bit ARM support to arch/x86? AFAIK some of the
machines are going to be basically PCs, including legacy I/O, ACPI
and UEFI, so they are much closer to that than they are to anything
in arch/arm. The instruction set of course is different, but you
already said that this
On Wednesday 11 July 2012, James Bottomley wrote:
Hi All,
We have set aside the second day of the kernel summit (Tuesday 28
August) as mini-summit day. So far we have only the PCI mini summit on
this day, so if you can think of other topics, please send them to the
kernel summit discuss
This was introduced in commit
876989d (mfd: Add device tree probe support for mc13xxx)
for spi and later while introducing support for i2c copied to the i2c
driver.
Modifying driver details is very strange, for example probing an
mc13892 device (instantiated via dt) removes the driver's
On Wed, 2012-07-11 at 12:33 +0200, Kay Sievers wrote:
Hey Joe,
what do you think of this?
It would make composing continuation lines at the caller side entirely
race-free, and it might fit into the usual pattern.
The more interesting thing, this would allow us to completely race-free
On 07/11/2012 02:18 PM, Christian Borntraeger wrote:
On 11/07/12 13:04, Avi Kivity wrote:
On 07/11/2012 01:17 PM, Christian Borntraeger wrote:
On 11/07/12 11:06, Avi Kivity wrote:
[...]
Almost all s390 kernels use diag9c (directed yield to a given guest cpu)
for spinlocks, though.
Perhaps
The tps65910 mfd driver has been converted to regmap APIs.
This patch adds tps65910_reg_update_bits() in include/linux/mfd/tps65910.h.
Thus we can use tps65910_reg_read/tps65910_reg_write/tps65910_reg_update_bits
directly and remove tps65910_reg_[read|modify_bits|read_locked|write_locked]
-Original Message-
From: iommu-boun...@lists.linux-foundation.org [mailto:iommu-
boun...@lists.linux-foundation.org] On Behalf Of Joerg Roedel
Sent: Wednesday, July 11, 2012 4:19 PM
To: io...@lists.linux-foundation.org
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH 2/7]
This is a fix for bug, introduced in 3.4 kernel by commit
1ab5ecb90cb6a3df1476e052f76a6e8f6511cb3d, which, among other things, replaced
simple sock_put() by sk_release_kernel(). Below is sequence, which leads to
oops for non-persistent devices:
tun_chr_close()
tun_detach()
On 07/11/2012 02:23 PM, Jan Kiszka wrote:
I'd appreciate a couple of examples for formality's sake.
From the top of my head: NVIDIA FX3700 (granted, legacy by now), Atheros
AR9287. For others, I need to check.
Thanks.
And then there is not easily replaceable legacy hardware like old
On 11.07.2012, at 13:23, Avi Kivity wrote:
On 07/11/2012 02:16 PM, Alexander Graf wrote:
yes the data structure itself seems based on the algorithm
and not on arch specific things. That should work. If we move that to
common
code then s390 will use that scheme automatically for the
On 07/11/2012 03:47 PM, Christian Borntraeger wrote:
On 11/07/12 11:06, Avi Kivity wrote:
[...]
Almost all s390 kernels use diag9c (directed yield to a given guest cpu) for
spinlocks, though.
Perhaps x86 should copy this.
See arch/s390/lib/spinlock.c
The basic idea is using several
On 11/07/12 13:51, Raghavendra K T wrote:
Almost all s390 kernels use diag9c (directed yield to a given guest cpu)
for spinlocks, though.
Perhaps x86 should copy this.
See arch/s390/lib/spinlock.c
The basic idea is using several heuristics:
- loop for a given amount of loops
- check if
On 07/11/2012 04:48 PM, Avi Kivity wrote:
On 07/11/2012 01:52 PM, Raghavendra K T wrote:
On 07/11/2012 02:23 PM, Avi Kivity wrote:
On 07/09/2012 09:20 AM, Raghavendra K T wrote:
Signed-off-by: Raghavendra K Traghavendra...@linux.vnet.ibm.com
Noting pause loop exited vcpu helps in filtering
On Wed, Jul 11, 2012 at 12:28:29PM +0100, Arnd Bergmann wrote:
On Wednesday 11 July 2012, James Bottomley wrote:
Hi All,
We have set aside the second day of the kernel summit (Tuesday 28
August) as mini-summit day. So far we have only the PCI mini summit on
this day, so if you can
The S2MPS11 is comprised of high efficient Buck converters,
various LDOs, and an RTC and tightly coupled with Multi Core Samsung
Application Processors, which is used in a wide variety of mobile applications
such as smart phones and tablet PCs.
S2MPS11 provide 10 high efficiency buck converters
Previous naming rule of samsung pmic start with s5m prefix.
But It is changed by s2m.
To cover various samsung s2m and s5m series,
This patch modify function and variable name for common usage.
Signed-off-by: Sangbeom Kim sbki...@samsung.com
---
drivers/mfd/sec-core.c | 130
As Prefix of Samsung pmic changed from s5m to s2m,
To make common mfd driver for s2m and s5m series,
This patch rename header of Samsung mfd and modify mfd driver.
Signed-off-by: Sangbeom Kim sbki...@samsung.com
---
drivers/mfd/sec-core.c |6 +-
drivers/mfd/sec-irq.c
On 07/11/2012 05:25 PM, Christian Borntraeger wrote:
On 11/07/12 13:51, Raghavendra K T wrote:
Almost all s390 kernels use diag9c (directed yield to a given guest cpu) for
spinlocks, though.
Perhaps x86 should copy this.
See arch/s390/lib/spinlock.c
The basic idea is using several
This patch add Samsung S2MPS11 mfd driver.
The S2MPS11 can support regulators and RTC.
Signed-off-by: Sangbeom Kim sbki...@samsung.com
---
drivers/mfd/sec-core.c | 10 ++
include/linux/mfd/samsung/core.h| 10 ++
include/linux/mfd/samsung/s2mps11.h | 196
On Wed, Jul 11, 2012 at 5:57 PM, Peter Zijlstra a.p.zijls...@chello.nl wrote:
On Wed, 2012-07-11 at 10:06 +0800, Yan, Zheng wrote:
This doesn't work. The MSRs for Cbox 8/9 in WSM-EX aren't contiguous with
Cbox 0~7.
Argh!
Furthermore the encoding for the FVC register in the Mbox are
This patch add Samsung S2MPS11 regulator driver.
The S2MPS11 can support 10 Bucks and 38 LDOs and RTC.
Especially, S2MPS11 is designed for high performance
Samsung application processor.
Signed-off-by: Sangbeom Kim sbki...@samsung.com
---
drivers/regulator/Kconfig |8 +
There are many samsung multifunction devices which are
s2mps11, s5m8767, s5m8763 etc.
This devices can support regulator, rtc, charger.
I will be supporting the Samsung mfd drivers, that are currently
in development and will be upstreamed shortly.
Signed-off-by: Sangbeom Kim sbki...@samsung.com
This patch support irq handling driver for s2mps11.
As this patch use regmap_irq, s5m8767 and s5m8763 are modified with
regmap_irq.
Signed-off-by: Sangbeom Kim sbki...@samsung.com
---
drivers/mfd/Kconfig |1 +
drivers/mfd/sec-irq.c| 477
File: rtl_nic/rtl8168g-1.fw
Version: 0.0.2
Change the ocp_base of linux driver to OCP_STD_PHY_BASE after setting
firmware. The firmware would modify the ocp_base, and that results the
driver uses the wrong ocp_base to access standard phy after setting
firmware.
Signed-off-by: Hayes Wang
On Wed, Jul 11, 2012 at 04:30:06PM +0800, Gao feng wrote:
there are some out of bound accesses in netprio cgroup.
now before accessing the dev-priomap.priomap array,we only check
if the dev-priomap exist.and because we don't want to see
additional bound checkings in fast path, so we should
Hi Russell,
On Thu, Jul 5, 2012 at 10:50 AM, Gupta, Ramesh grgu...@ti.com wrote:
From 393c4effbbec74ff9b969d53ce4d36fde56b71df Mon Sep 17 00:00:00 2001
From: Ramesh Gupta G grgu...@ti.com
Date: Wed, 4 Jul 2012 16:43:41 +0530
Subject: [PATCH v4 0/2] add new cache maintenance api
This patch
On 07/10/2012 06:43 PM, John Stultz wrote:
clock_was_set() cannot be called from hard interrupt context because
it calls on_each_cpu(). For fixing the widely reported leap seconds
issue it's necessary to call it from the timer interrupt context.
Provide a new function which denotes it in
On 07/10/2012 06:43 PM, John Stultz wrote:
Over the weekend, Thomas got a chance to review the leap second fix
in more detail and had a few additional changes he wanted to make
to improve performance as well as style.
So this iteration includes his modifications.
Once merged, I'll be
Hello.
On 10-07-2012 10:32, Gerard Snitselaar wrote:
commit ff9cce82 added back 2 lines that were removed by commit
c83a8542
Please also specify the summaries of those 2 commits in parens.
causing build of twl6030-usb to get an error due to otg being
referenced, but not declared. This
Hi Sethi,
On Wed, Jul 11, 2012 at 11:47:39AM +, Sethi Varun-B16395 wrote:
I am currently working on upstreaming the Freescale IOMMU driver. As
discussed (with Scott Wood) a while back, this representation of the
GEOMETRY attribute doesn't go well with our IOMMU implementation. Our
Hi,
Hi Masatake,
On Wed, Jul 11, 2012 at 01:58:31PM +0900, Masatake YAMATO wrote:
(The patch sets are rebased to bluetooth-next. Unnecessary white
spaces are trimmed.)
lsof command can tell the type of socket processes are using.
Internal lsof uses inode numbers on socket fs to resolve
Fix typo for case REGULATOR_STATUS_STANDBY - REGULATOR_MODE_STANDBY.
For undefined mode, return REGULATOR_STATUS_ERROR (0 is not valid status).
Signed-off-by: Krystian Garbaciak krystian.garbac...@diasemi.com
---
drivers/regulator/core.c |4 ++--
1 files changed, 2 insertions(+), 2
H Hartley Sweeten's recent series of patches to clean up the rtd520
driver made some of the register accesses harder to understand. Add a
few comments to provide some clues to the reader.
Signed-off-by: Ian Abbott abbo...@mev.co.uk
Cc: H Hartley Sweeten hswee...@visionengravers.com
Cc: Greg
Hi,
I see the same build-error as Randy in latest linux.git
(055c9fa8874fa7261eec7a268366565db84af474).
Where is this patch queued up (see original posting)?
I do not see any patch in [2].
And please please please rename your repo... linux-2.6 died many
months ago :-).
I also do not see any
--- /dev/null
+++ b/include/linux/mfd/samsung/core.h
@@ -0,0 +1,147 @@
+/*
+ * core.h
+ *
+ * copyright (c) 2011 Samsung Electronics Co., Ltd
+ * http://www.samsung.com
In most of the files you mentioned 2011.
Should they not be changed to 2012?
+ *
+ * This program is
No waiting is needed for mac_ocp_{write / read}. And the bit 31 of
OCPDR would not change, so rtl_udelay_loop_wait_high always return
false. That is, the r8168_mac_ocp_read always retuen ~0.
Signed-off-by: Hayes Wang hayesw...@realtek.com
---
drivers/net/ethernet/realtek/r8169.c | 12
On Wednesday 11 July 2012, Roland Stigge wrote:
Thanks for the note! Looks like the interface consolidated to replace
ch-cd-min_signal with sth. like cd-min_signal directly.
Accessing the signal id/number is/was quite convenient because as you
can see in the 3 above cases that now get
On Wed, Jul 11, 2012 at 12:49:24AM -0700, Paul E. McKenney wrote:
On Tue, Jul 10, 2012 at 12:47:00PM +0800, Fengguang Wu wrote:
Hi Paul,
Fortunately this bug is bisectable and the first bad commit is:
commit 9b2e4f1880b789be1f24f9684f7a54b90310b5c0
Author: Paul E.
On 07/11/2012 02:33 PM, Arnd Bergmann wrote:
On Wednesday 11 July 2012, Roland Stigge wrote:
Thanks for the note! Looks like the interface consolidated to replace
ch-cd-min_signal with sth. like cd-min_signal directly.
Accessing the signal id/number is/was quite convenient because as you
can
- Original Message -
Hm, suppose we're the next-in-line for a ticket lock and exit due
to
PLE. The lock holder completes and unlocks, which really assigns
the
lock to us. So now we are the lock owner, yet we are marked as
don't
yield-to-us in the PLE code.
Yes..
On Wed, 11 Jul 2012, Prarit Bhargava wrote:
On 07/10/2012 06:43 PM, John Stultz wrote:
clock_was_set() cannot be called from hard interrupt context because
it calls on_each_cpu(). For fixing the widely reported leap seconds
issue it's necessary to call it from the timer interrupt context.
On 07/11/2012 02:52 PM, Alexander Graf wrote:
On 11.07.2012, at 13:23, Avi Kivity wrote:
On 07/11/2012 02:16 PM, Alexander Graf wrote:
yes the data structure itself seems based on the algorithm
and not on arch specific things. That should work. If we move that to
common
code then
于 2012年07月11日 20:11, Neil Horman 写道:
On Wed, Jul 11, 2012 at 04:30:06PM +0800, Gao feng wrote:
there are some out of bound accesses in netprio cgroup.
now before accessing the dev-priomap.priomap array,we only check
if the dev-priomap exist.and because we don't want to see
additional bound
On Wed, Jul 11, 2012 at 01:07:17PM +0300, Valentin, Eduardo wrote:
Hello Greg,
On Mon, Jul 9, 2012 at 11:33 PM, Valentin, Eduardo
eduardo.valen...@ti.com wrote:
Hello Greg,
On Mon, Jul 9, 2012 at 10:31 PM, Greg Kroah-Hartman
gre...@linuxfoundation.org wrote:
On Sat, Jul 07, 2012 at
On Wed, Jul 11, 2012 at 08:36:16PM +0800, Fengguang Wu wrote:
On Wed, Jul 11, 2012 at 12:49:24AM -0700, Paul E. McKenney wrote:
On Tue, Jul 10, 2012 at 12:47:00PM +0800, Fengguang Wu wrote:
Hi Paul,
Fortunately this bug is bisectable and the first bad commit is:
commit
[34323.844970] [ cut here ]
[34323.84] kernel BUG at kernel/timer.c:711!
[34323.846110] invalid opcode: [#1] PREEMPT SMP
[34323.846657] CPU 6
[34323.846670] Modules linked in:
[34323.853968] ebtables
[34323.866941] xt_cpu
[34323.890355] msdos
[34323.920927]
On Wed, Jul 11, 2012 at 10:36:46AM +0200, Bjørn Mork wrote:
Greg Kroah-Hartman gre...@linuxfoundation.org writes:
On Tue, Jul 10, 2012 at 06:51:03PM -0300, Gustavo Padovan wrote:
{ USB_VENDOR_AND_INTERFACE_INFO(0x0a5c, 0xff, 0x01, 0x01) }
Two entries in the cdc_wdm driver can also be
On Wed, 2012-07-11 at 14:45 +0200, Thomas Gleixner wrote:
On Wed, 11 Jul 2012, Prarit Bhargava wrote:
On 07/10/2012 06:43 PM, John Stultz wrote:
clock_was_set() cannot be called from hard interrupt context because
it calls on_each_cpu(). For fixing the widely reported leap seconds
I wish there was a nicer way to do this ... but looking at the code I can't
figure out a better way. (no offense John, it's just the way the code is ;)
)
Yeah, I had the same discussion with Peter earlier today. There is
only a rather limited set of options.
1) Retrigger the timer
On 07/11/2012 05:21 PM, Raghavendra K T wrote:
On 07/11/2012 03:47 PM, Christian Borntraeger wrote:
On 11/07/12 11:06, Avi Kivity wrote:
[...]
So there is no win here, but there are other cases were diag44 is
used, e.g. cpu_relax.
I have to double check with others, if these cases are
According to the Wikipedia article on CUBIC, it's used in Linux kernels
2.6.19 and above. Is that still the case? Are there any plans to use a
different algorithm in the foreseeable future?
Is it as described in the 2008 ACM SIGOPS paper by Ha, Rhee and Xu:
On Wed, 11 Jul 2012 12:57:55 +0100, Catalin Marinas
catalin.mari...@arm.com wrote:
On Wed, Jul 11, 2012 at 12:28:29PM +0100, Arnd Bergmann wrote:
On Wednesday 11 July 2012, James Bottomley wrote:
Hi All,
We have set aside the second day of the kernel summit (Tuesday 28
August) as
On 07/11/2012 04:06 AM, Axel Lin wrote:
Current code has been converted to use regmap APIs, the io_mutex is not
needed.
Thus remove the io_mutex.
Signed-off-by: Axel Lin axel@gmail.com
Thanks for cleanup,
Acked-by: Peter Ujfalusi peter.ujfal...@ti.com
--
To unsubscribe from this
Looks nice.. How about something like the below on top.. I couldn't
immediately find a sane reason for the grand-parent to always be red in
the insertion case.
---
--- a/lib/rbtree.c
+++ b/lib/rbtree.c
@@ -23,6 +23,25 @@
#include linux/rbtree.h
#include linux/export.h
+/*
+ * red-black trees
From: Wanpeng Li l...@linux.vnet.ibm.com
Since hierachical_memory_limit shows of bytes of memory limit with
regard to hierarchy under which the memory cgroup is, the count should
calculate max hierarchy limit when use_hierarchy in order to show hierarchy
subtree limit. hierachical_memsw_limit is
On Wednesday 11 July 2012, Roland Stigge wrote:
OK, thanks!
Is a patch on top of the already provided lpc32xx-next branches the
preferred form for a fix? On top of which branch do you need it?
Yes, I think in this case, changing it on top of that branch is best.
I'm not sure how that
On Wed, Jul 11, 2012 at 01:10:01PM +0100, Krystian Garbaciak wrote:
Fix typo for case REGULATOR_STATUS_STANDBY - REGULATOR_MODE_STANDBY.
For undefined mode, return REGULATOR_STATUS_ERROR (0 is not valid status).
This is deliberate. It's not reporting an error, it's reporting an
indeterminate
-Original Message-
From: Joerg Roedel [mailto:joerg.roe...@amd.com]
Sent: Wednesday, July 11, 2012 5:47 PM
To: Sethi Varun-B16395
Cc: io...@lists.linux-foundation.org; linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/7] iommu/amd: Implement DOMAIN_ATTR_GEOMETRY
attribute
Hi
On Wed, 2012-07-11 at 12:11 +0200, Jan Kara wrote:
So case 2.b is a bit controversial, but I think it is acceptable. After
all, by
enabling checksumming we already sign up for paying the price of
calculating
it. The way to improve checksumming performance globally would be to
Hi Hans,
Thank you for your review
+static int adv7180_init_controls(struct adv7180_state *state)
+{
+ v4l2_ctrl_handler_init(state-ctrl_hdl, 2);
2 - 4, since there are 4 controls. It's a hint only, but it helps
optimizing the internal hash data structure.
Sure :)
@@ -445,9
On 06/21/2012 04:48 AM, Xiao Guangrong wrote:
On 06/20/2012 10:11 PM, Takuya Yoshikawa wrote:
We can change the debug message later if needed.
Actually, i am going to use tracepoint instead of
these debug code.
Yes, these should be in the kvmmmu namespace.
--
error compiling
On 7/11/12 3:53 AM, Gleb Natapov wrote:
On Wed, Jul 11, 2012 at 11:49:47AM +0200, Peter Zijlstra wrote:
On Wed, 2012-07-11 at 10:10 +0300, Gleb Natapov wrote:
Looks like Avi is right about the overshoot. Can you test something like this?
I head to the airport in a few minutes; I'll try it
Hello,
we've recently hit a deadlock in our QA runs which is caused by the
per-process plugging code. The problem is as follows:
process A process B (kjournald)
generic_file_aio_write()
blk_start_plug(plug);
...
somewhere in here we allocate
I am working on a kernel module to monitor all TCP packets. I created a protocol
handler with protocol code ETH_P_ALL to handle all incoming and outgoing
TCP packets. The code worked fine on 2.6.14 kernel, but in current 3.2.0-26
kernel, I am no longer able to get the TCP payload for outgoing
On Wed, 2012-07-11 at 09:05 -0400, Prarit Bhargava wrote:
Both of those options seem like a lot of work for something that happens once
every 3-4 years, and may not happen ever again[1]. Based on that statement,
if
we're going to modify code I would prefer that it be as lightweight as
On 07/11/2012 03:25 PM, Arnd Bergmann wrote:
On Wednesday 11 July 2012, Roland Stigge wrote:
OK, thanks!
Is a patch on top of the already provided lpc32xx-next branches the
preferred form for a fix? On top of which branch do you need it?
Yes, I think in this case, changing it on top of
This step makes it very easy to keep track about the current
intialization state of the iommu driver. With this change we
can initialize the IOMMU hardware to a point where it can
remap interrupts and later resume the initializion to enable
dma remapping.
Signed-off-by: Joerg Roedel
Add routines to:
* Alloc remapping tables and single entries from these
tables
* Change entries in the tables
* Free entries in the table
Signed-off-by: Joerg Roedel joerg.roe...@amd.com
---
drivers/iommu/amd_iommu.c | 230 +
1 file changed, 230
Report the availability of irq remapping through the
IOMMU-API to allow KVM device passthrough again without
additional module parameter overrides.
Signed-off-by: Joerg Roedel joerg.roe...@amd.com
---
drivers/iommu/amd_iommu.c |2 ++
1 file changed, 2 insertions(+)
diff --git
Hi,
here is the second and revised patch-set to add interrupt remapping
support to the AMD IOMMU driver.
Changes v1-v2:
* Improved print_iommu_info() function as suggested by Joe
Perches
* Fixed all five problems reported by Fengguang Wu from Intel,
thanks
The irq remapping tables for the AMD IOMMU need to be
aligned on a 128 byte boundary. Create a seperate slab-cache
to guarantee this alignment.
Signed-off-by: Joerg Roedel joerg.roe...@amd.com
---
drivers/iommu/amd_iommu.c |2 ++
drivers/iommu/amd_iommu_init.c | 23
Do not deinitialize the AMD IOMMU driver completly when
interrupt remapping is already in use but the initialization
of the DMA layer fails for some reason. Make sure the IOMMU
can still be used to remap interrupts.
Signed-off-by: Joerg Roedel joerg.roe...@amd.com
---
Add routines to setup interrupt remapping for MSI
interrupts.
Signed-off-by: Joerg Roedel joerg.roe...@amd.com
---
drivers/iommu/amd_iommu.c | 74 +
1 file changed, 74 insertions(+)
diff --git a/drivers/iommu/amd_iommu.c b/drivers/iommu/amd_iommu.c
The IVRS table usually includes the IOMMU device. But the
IOMMU does never translate itself, so make sure the IOMMU
driver knows this.
Signed-off-by: Joerg Roedel joerg.roe...@amd.com
---
drivers/iommu/amd_iommu_init.c |7 +++
1 file changed, 7 insertions(+)
diff --git
Print an indicator to dmesg to easily find out if interrupt
remapping is enabled of a given system.
Signed-off-by: Joerg Roedel joerg.roe...@amd.com
---
drivers/iommu/amd_iommu_init.c |2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/iommu/amd_iommu_init.c
801 - 900 of 1348 matches
Mail list logo
