Add twl4030-usb data node in twl4030 device tree file.
Signed-off-by: Kishon Vijay Abraham I
---
arch/arm/boot/dts/twl4030.dtsi | 21 +
1 file changed, 21 insertions(+)
diff --git a/arch/arm/boot/dts/twl4030.dtsi b/arch/arm/boot/dts/twl4030.dtsi
index 22f4d13..761a5a5
Add usb otg data node in omap4/omap3 device tree file. Also update
the node with board specific setting in omapx-.dts file.
Signed-off-by: Kishon Vijay Abraham I
---
arch/arm/boot/dts/omap3-beagle.dts |6 ++
arch/arm/boot/dts/omap3-evm.dts|6 ++
arch/arm/boot/dts/omap3.dtsi
The mailbox register for usb otg in omap is present in control module.
On detection of any events VBUS or ID, this register should be written
to send the notification to musb core.
Till we have a separate control module driver to write to control module,
omap2430 will handle the register writes
All phy related programming like enabling/disabling the clocks, powering
on/off the phy is taken care of by this driver. It is also used for OTG
related functionality like srp.
This also includes device tree support for usb2 phy driver and
the documentation with device tree binding information is
Add omap-usb2 data node in omap4 device tree file.
Signed-off-by: Kishon Vijay Abraham I
---
arch/arm/boot/dts/omap4.dtsi |5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm/boot/dts/omap4.dtsi b/arch/arm/boot/dts/omap4.dtsi
index 29c6243..15f1890 100644
---
All the PHY configuration other than VBUS, ID GND and OTG SRP are removed
from twl6030. The phy configurations are taken care by the dedicated
usb2 phy driver. So twl6030 is made as comparator driver for VBUS and
ID detection.
Writing to control module which is now handled in omap2430.c should be
This patch series adds device tree support for MUSB and device
tree support for all the related modules to get MUSB working in
OMAP platform.
A new omap-usb2 phy driver has been added (with only dt suppport)
to perform phy configurations. Previously this configuration was
performed by twl6030,
All the unnessary functions in omap-phy-internal is removed.
These functionality are now handled by omap-usb2 phy driver.
Cc: Felipe Balbi
Signed-off-by: Kishon Vijay Abraham I
Acked-by: Tony Lindgren
---
arch/arm/mach-omap2/omap_phy_internal.c | 138 ---
On Thu, 2012-07-19 at 09:42 -0500, Seth Jennings wrote:
> This patch adds the driver for interacting with the 842
> compression accelerator on IBM Power7+ systems.
...
> +struct nx842_slentry {
> + unsigned long ptr; /* Absolute address (use virt_to_abs()) */
> /+unsigned long len;
> +};
Hello, Steven,
(Sorry for the late reply.)
Tnank you for your comments.
(2012/07/12 8:26), Steven Rostedt wrote:
+Snapshot
+
+If CONFIG_TRACER_MAX_TRACE is set, the (generic) snapshot
+feature is available in all tracers except for the special
+tracers which use a snapshot inside
Hi all,
Changes since 20120719:
The scsi tree gained a conflict against Linus' tree and a build failure
for which I reverted a commit.
The net-next tree lost a conflict.
The tty tree lost its build failure but gained 3 more for which I
disabled 2 staging drivers and applied a patch
Hi all,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
drivers/usb/serial/console.c: In function 'usb_console_setup':
drivers/usb/serial/console.c:168:16: error: invalid type argument of '->' (have
'struct ktermios')
Hello Vivek,
On Thu, 19 Jul 2012 09:49:21 -0400
Vivek Goyal wrote:
> On Wed, Jul 18, 2012 at 03:04:39PM -0700, Andrew Morton wrote:
> > On Tue, 17 Jul 2012 13:36:55 -0400
> > Vivek Goyal wrote:
> >
> > > Last line of vmcoreinfo note does not end with \n. Parsing all the lines
> > > in note
On Thu, Jul 19, 2012 at 11:28 AM, Attila Kinali wrote:
> Hi,
>
> I'm working on an embedded system based on a Freescale ARM9 processor i.mx23.
>
> While trying linux-next i stumpled over my login prompt getting broken.
> What exactly happens is that the kernel boots normally, but when my
> login
Dear Linux hackers,
Sorry for the intrusion on this technical list. I wanted to let Andre's fellow
Linux developers know that he died this past weekend. For those that don't know
him, Andre was an active developer for the ATA driver a while back.
I have known Andre for about 9 years, although
This function does not exist, remove the extern function declaration.
Signed-off-by: Axel Lin
---
drivers/regulator/mc13xxx.h |1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/regulator/mc13xxx.h b/drivers/regulator/mc13xxx.h
index 8343a25..eaff551 100644
---
On Wed, Jul 18, 2012 at 10:10 AM, Mark Brown
wrote:
> On Tue, Jul 17, 2012 at 07:57:49PM +0100, Mark Brown wrote:
>> -next fails to boot for me today on my s3c64xx based systems. Walking
>> back to the last time I tried and bisecting likely branches I find that
>> commit 910139 (irqdomain:
On Fri, Jul 20, 2012 at 12:19:20PM +0900, Kamezawa Hiroyuki wrote:
> (2012/07/20 8:34), Tim Chen wrote:
> >Hi,
> >
> >I noticed in a multi-process parallel files reading benchmark I ran on a
> >8 socket machine, throughput slowed down by a factor of 8 when I ran
> >the benchmark within a cgroup
Hi Shashidhar,
On Wed, Jul 18 2012, Shashidhar Hiremath wrote:
> I want to use printascii to debug my serial driver. How do I enable
> it and use the feature.
> Currently I have enabled in menuconfig and done an extern on the
> printascii api, this doesn't seem to work, So any hints for
On Thu, 2012-07-19 at 10:02 -0400, Steven Rostedt wrote:
> On Thu, 2012-07-19 at 15:51 +0200, Mike Galbraith wrote:
>
> > Every kernel I've fed you script to has died sooner or later, so I wish
> > him fair sailing. Here there be sea monsters ;-)
>
> I'm curious. Can my script bring down a
BTW, they are some bug fix patches on -master branch, but
it is not existed on -next branch:
commit: f411930442e01f9cf1bf4df41ff7e89476575c4d
commit: 85b7059169e128c57a3a8a3e588fb89cb2031da1
It causes code conflict if we do the development on -next.
On 07/20/2012 08:39 AM, Marcelo Tosatti
[Sent again due to problems with email client]
Hi,
On 07/20/2012 04:01 AM, Stephen Rothwell wrote:
Hi all,
After merging the net-next tree, today's linux-next build (powerpc
pmac32_defconfig) failed like this:
ERROR: "phy_disconnect" [drivers/net/usb/asix.ko] undefined!
ERROR: "phy_stop"
I am working on ARM architecture.
On Wed, Jul 18, 2012 at 9:33 PM, Randy Dunlap wrote:
> On 07/18/2012 06:03 AM, Shashidhar Hiremath wrote:
>
>> HI,
>> I want to use printascii to debug my serial driver. How do I enable
>> it and use the feature.
>> Currently I have enabled in menuconfig and
Hi Greg,
After merging the tty tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
drivers/staging/serqt_usb2/serqt_usb2.c: In function 'qt_set_termios':
drivers/staging/serqt_usb2/serqt_usb2.c:1198:29: error: incompatible types when
initializing type 'struct ktermios *'
Hi Greg,
After merging the tty tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
drivers/staging/ipack/devices/ipoctal.c: In function 'ipoctal_set_termios':
drivers/staging/ipack/devices/ipoctal.c:614:22: error: invalid type argument of
'->' (have 'struct ktermios')
(2012/07/20 8:34), Tim Chen wrote:
Hi,
I noticed in a multi-process parallel files reading benchmark I ran on a
8 socket machine, throughput slowed down by a factor of 8 when I ran
the benchmark within a cgroup container. I traced the problem to the
following code path (see below) when we are
A large enough symbol size causes an overflow in the size parameter to the
histogram allocation, leading to a segfault in symbol__inc_addr_samples later
on when this histogram is accessed.
In the case of being called via perf-report, this returns back and
gracefully ignores the sample, eventually
On Fri, Jul 20, 2012 at 12:39:24AM +, Seiji Aguchi wrote:
>
> Thank you for describing this in detail.
>
> > Yes - if the OOPs is instrumental in the path leading to the hang/panic -
> > then the OOPS is the first place to look for the root cause of
> > the problem. But it will be a case by
When io access mode is enabled by BOOTROM or BIOS for AR8152 v2.1,
the register can't be read/write by memory access mode.
Clearing Bit 8 of Register 0x21c could fixed the issue.
Signed-off-by: Cloud Ren
Cc: stable
Signed-off-by: xiong
---
drivers/net/ethernet/atheros/atl1c/atl1c_hw.h |
On 07/19/2012 06:16 PM, Avi Kivity wrote:
> On 07/17/2012 05:45 PM, Xiao Guangrong wrote:
>> In the later patch, it indicates failure when we try to get a writable
>> hva from the readonly slot
>>
>> Signed-off-by: Xiao Guangrong
>> ---
>> virt/kvm/kvm_main.c | 12 +++-
>> 1 files
struct annotation *notes = symbol__annotation(sym);
const size_t size = symbol__size(sym);
- size_t sizeof_sym_hist = (sizeof(struct sym_hist) + size * sizeof(u64));
+ size_t sizeof_sym_hist;
+
+ /* Check for overflow when calculating sizeof_sym_hist */
+
On 07/19/2012 06:15 PM, Avi Kivity wrote:
> On 07/17/2012 05:44 PM, Xiao Guangrong wrote:
>> Introduce readonly_fault_pfn, in the later patch, it indicates failure
>> when we try to get a writable pfn from the readonly memslot
>>
>> +
>> inline int kvm_is_mmio_pfn(pfn_t pfn)
>> {
>> if
From: Jonghwa Lee
The policy might have been changed since last call of target().
Thus, using cpufreq_frequency_table_target(), which depends on
policy to find the corresponding index from a frequency, may return
inconsistent index for freqs.old. Thus, old_index should be
calculated not based on
+ /* Check for overflow when calculating sizeof_sym_hist */
+ if (size > (SIZE_MAX / sizeof(u64)))
+ return -1;
How does it guarantee that the end result which used in zalloc below
would not overflow?
+
+ sizeof_sym_hist = (sizeof(struct sym_hist) + size *
A large enough symbol size causes an overflow in the size parameter to the
histogram allocation, leading to a segfault in symbol__inc_addr_samples later
on when this histogram is accessed.
In the case of being called via perf-report, this returns back and
gracefully ignores the sample, eventually
On Fri, 20 Jul 2012 12:01:18 +1000 Stephen Rothwell
wrote:
>
> After merging the net-next tree, today's linux-next build (powerpc
> pmac32_defconfig) failed like this:
This was actually yesterday's linux-next - I guess it is fixed by commit
215029375c83 ("asix: AX88172A driver depends on
On Thu, 19 Jul 2012, Ben Hutchings wrote:
On Thu, Jul 19, 2012 at 06:30:47PM +0100, Alan Cox wrote:
For the end user case you need the distro to plonk the right file in the
right place and be done with it, once they do that the rest is
bikeshedding a ten line Makefile rule.
This might work
On 07/20/2012 08:39 AM, Marcelo Tosatti wrote:
> On Tue, Jul 17, 2012 at 09:53:29PM +0800, Xiao Guangrong wrote:
>> If it have no indirect shadow pages we need not protect any gfn,
>> this is always true for direct mmu without nested
>>
>> Signed-off-by: Xiao Guangrong
>
> Xiao,
>
> What is the
I got this oops & stack overrun warning while running mkfs.ext4 on a sparse 4T
file hosted on xfs.
Should CFQ be issuing IO here?
-Eric
[10821.639839] BUG: unable to handle kernel paging request at fffb900148a0
[10821.640820] IP: [] cpuacct_charge+0xb4/0x210
[10821.640820] PGD 1c0d067 PUD
On 07/20/2012 08:03 AM, Marcelo Tosatti wrote:
> On Tue, Jul 17, 2012 at 09:52:13PM +0800, Xiao Guangrong wrote:
>> Introduce set_mmio_exit_info to cleanup the common code
>>
>> Signed-off-by: Xiao Guangrong
>> ---
>> arch/x86/kvm/x86.c | 33 +
>> 1 files
Hi Al,
Would you please fold the below fix to commit 5c781a65fff ("vfs:
Create function for iterating over block devices")?
Thanks,
Fengguang
---
Subject: [PATCH] sync: fix build error on iterate_bdevs()
fs/sync.c:110:2: error: implicit declaration of function 'iterate_bdevs'
---
On 07/20/2012 07:58 AM, Marcelo Tosatti wrote:
>> -}
>> +rc = ctxt->ops->read_emulated(ctxt, addr, mc->data + mc->end, size,
>> + >exception);
>> +if (rc != X86EMUL_CONTINUE)
>> +return rc;
>> +
>> +mc->end += size;
>> +
>>
Hi all,
After merging the net-next tree, today's linux-next build (powerpc
pmac32_defconfig) failed like this:
ERROR: "phy_disconnect" [drivers/net/usb/asix.ko] undefined!
ERROR: "phy_stop" [drivers/net/usb/asix.ko] undefined!
ERROR: "phy_ethtool_gset" [drivers/net/usb/asix.ko] undefined!
ERROR:
Running one program that continuously hotplugs and replugs a cpu
concurrently with another program that continuously writes to the
scaling_setspeed node eventually deadlocks with:
=
[ INFO: possible recursive locking detected ]
3.4.0 #37 Tainted: G
On 07/16/2012 04:29 PM, Alex Shi wrote:
> On 07/16/2012 03:40 PM, Rusty Russell wrote:
>
>> On Mon, 16 Jul 2012 10:35:54 +0800, Alex Shi wrote:
>>> The function has no parameter @len now, so need to remove it from
>>> comments to avoid kernel-doc warning:
>>
>> But it still does in my tree.
>>
On Tue, Jul 17, 2012 at 10:40:21PM -0300, Paulo Alcantara wrote:
> From: Christoph Hellwig
> Date: Tue, 17 Jul 2012 03:06:43 -0400
>
> > Btw, if you need more reviers for the syslinus support feel free to pass
> > it by me (or the list).
>
> This is the branch I'm maintaing for the XFS readonly
Hi Oliver:
I will fix it. Should I resend all three patches, or just this one?
BR,
Wei WANG
于 2012年07月19日 20:26, Oliver Neukum 写道:
> On Thursday 19 July 2012 17:55:18 wei_w...@realsil.com.cn wrote:
>
>> +static void sd_normal_rw(struct realtek_sdmmc *host, struct mmc_request
>> *mrq)
>> +{
>>
On Thu, 2012-07-19 at 16:07 -0700, H. Peter Anvin wrote:
> On 07/19/2012 04:04 PM, Steven Rostedt wrote:
>
> > Basically, all we want to do is add 8 to the stack pointer. And this is
> > for the x86_32 version of whatever hardware is in use.
> >
>
> What I'm telling you is that it depends on
The incompatible parameter of flush_tlb_mm_range cause build warning.
Fix it by correct parameter.
Reported-by: Tetsuo Handa
Signed-off-by: Alex Shi
---
arch/x86/include/asm/tlbflush.h |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/x86/include/asm/tlbflush.h
As we're no longer using the flag we don't need to extract the value from the
command line and store it. This is a step towards removing command line
parameter code.
Signed-off-by: Joe Millenbach
Signed-off-by: Gokul Caushik
Reviewed-by: Josh Triplett
---
arch/x86/boot/compressed/misc.c |
Change all instances of if (debug) putstr(...) to a new debug_putstr(...).
This allows a future change to conditionally stub out debug_putstr to save
space.
Signed-off-by: Joe Millenbach
Signed-off-by: Gokul Caushik
Reviewed-by: Josh Triplett
---
arch/x86/boot/compressed/misc.c | 18
From: Gokul Caushik
CONFIG_EARLY_PRINTK is the only feature that might use command line
parsing in the decompression stage. If it is disabled then we can
exclude the related code to save space. This can result in an estimated
space savings of 2240 bytes from the compressed kernel image.
Removes early_serial_console.c code if we don't have the config option that
enables it (EARLY_PRINTK). When disabling this code, make early_serial_base a
constant 0 to allow the compiler to optimize away the code that checks for
early_serial_base.
Signed-off-by: Joe Millenbach
Signed-off-by:
For consistency we changed the error output path to match the new debug path.
Signed-off-by: Joe Millenbach
Signed-off-by: Gokul Caushik
Reviewed-by: Josh Triplett
---
arch/x86/boot/compressed/misc.c |6 +++---
arch/x86/boot/compressed/misc.h |1 +
2 files changed, 4 insertions(+), 3
There are only 3 uses of the quiet flag and they all protect output that
is only useful for debugging the stub, therefore we switched to using the
debug flag for all extra output.
Signed-off-by: Joe Millenbach
Signed-off-by: Gokul Caushik
Reviewed-by: Josh Triplett
---
On Wed, Jul 18, 2012 at 09:47:34PM +0200, Rafael J. Wysocki wrote:
> On Wednesday, July 18, 2012, Todd Poynor wrote:
...
> > +{
> > + struct wakeup_source *ws;
> > + int active = 0;
> > + struct wakeup_source *last_activity_ws = NULL;
> > +
> > + rcu_read_lock();
> > +
Hi, Cody
On Thu, 19 Jul 2012 17:13:35 -0700, Cody Schafer wrote:
> A large enough symbol size causes an overflow in the size parameter to the
> histogram allocation, leading to a segfault in symbol__inc_addr_samples later
> on when this histogram is accessed.
>
> In the case of being called via
Separate is better. When I say clean patch I mean in a separate email so git
am can process it.
Alex Shi wrote:
>On 07/20/2012 07:56 AM, H. Peter Anvin wrote:
>
>> On 07/19/2012 04:52 PM, Alex Shi wrote:
>>>
>>> Sure, it is a bug, the fix had sent:
>>> https://lkml.org/lkml/2012/7/6/350
>>>
On Tue, Jul 17, 2012 at 09:52:52PM +0800, Xiao Guangrong wrote:
> It will trigger a WARN_ON if the page has been freed but it is still
> used in mmu, it can help us to detect mm bug early
>
> Signed-off-by: Xiao Guangrong
> ---
> arch/x86/kvm/mmu.c |8
> 1 files changed, 8
On Tue, Jul 17, 2012 at 09:51:34PM +0800, Xiao Guangrong wrote:
> No need split mmio read region into 8-bits pieces since we do it in
> emulator_read_write_onepage
>
> Signed-off-by: Xiao Guangrong
> ---
> arch/x86/kvm/emulate.c | 29 -
> 1 files changed, 12
Applied all patches except 2, 3 and 5, 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
Please read the FAQ at http://www.tux.org/lkml/
On Tue, Jul 17, 2012 at 09:53:29PM +0800, Xiao Guangrong wrote:
> If it have no indirect shadow pages we need not protect any gfn,
> this is always true for direct mmu without nested
>
> Signed-off-by: Xiao Guangrong
Xiao,
What is the motivation? Numbers please.
In fact, what case was the
On Tue, Jul 17, 2012 at 09:52:13PM +0800, Xiao Guangrong wrote:
> Introduce set_mmio_exit_info to cleanup the common code
>
> Signed-off-by: Xiao Guangrong
> ---
> arch/x86/kvm/x86.c | 33 +
> 1 files changed, 17 insertions(+), 16 deletions(-)
This makes the
> -Original Message-
> From: Greg KH (gre...@linuxfoundation.org)
> [mailto:gre...@linuxfoundation.org]
> Sent: Thursday, July 19, 2012 7:29 PM
> To: KY Srinivasan
> Cc: Paolo Bonzini; de...@linuxdriverproject.org; linux-kernel@vger.kernel.org;
> virtualizat...@lists.osdl.org
> Subject:
Hi James,
After merging the scsi tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
drivers/base/dd.c:27:28: fatal error: scsi/scsi_scan.h: No such file or
directory
Caused by commit eea03c20ae38 ("Make wait_for_device_probe() also do
scsi_complete_async_scans()") from
Thank you for describing this in detail.
> Yes - if the OOPs is instrumental in the path leading to the hang/panic -
> then the OOPS is the first place to look for the root cause of
> the problem. But it will be a case by case analysis.
> Sometimes the OOPS might be unconnected. If possible
On 07/19/2012 04:22 PM, Darren Hart wrote:
>
>
> On 07/13/2012 11:54 AM, Dave Jones wrote:
>> On Fri, Jul 13, 2012 at 08:47:38PM +0200, Thomas Gleixner wrote:
>> > On Fri, 13 Jul 2012, Dave Jones wrote:
>> >
>> > > Looks like calling futex() with garbage makes things unhappy.
>> >
>> >
> -Original Message-
> From: Anthony Liguori [mailto:anth...@codemonkey.ws]
> Sent: Thursday, July 19, 2012 7:18 PM
> To: KY Srinivasan
> Cc: Greg KH (gre...@linuxfoundation.org); Paolo Bonzini;
> de...@linuxdriverproject.org; linux-kernel@vger.kernel.org;
> virtualizat...@lists.osdl.org
Hi James,
Today's linux-next merge of the scsi tree got a conflict in
drivers/scsi/scsi_wait_scan.c between commit eea03c20ae38 ("Make
wait_for_device_probe() also do scsi_complete_async_scans()") from Linus'
tree and commit 01444e1106cb ("[SCSI] Remove scsi_wait_scan module") from
the scsi tree.
On Thu, Jul 19, 2012 at 06:58:38PM -0500, H Hartley Sweeten wrote:
> On Thursday, July 19, 2012 4:35 PM, gregkh wrote:
> > On Thu, Jul 19, 2012 at 06:31:23PM -0500, H Hartley Sweeten wrote:
> >> If the comedi pci drivers have the "attach_pci" callback defined, the
> >> PCI api does correctly probe
A large enough symbol size causes an overflow in the size parameter to the
histogram allocation, leading to a segfault in symbol__inc_addr_samples later
on when this histogram is accessed.
In the case of being called via perf-report, this returns back and
gracefully ignores the sample, eventually
On Wed, Jul 18, 2012 at 10:34 PM, Kim, Milo wrote:
> TI LP8788 PMU has the current sink as the keyboard led driver.
> The brightness is controlled by the i2c commands.
> Configurable parameters can be defined in the platform side.
>
> Signed-off-by: Milo(Woogyom) Kim
> ---
>
On 07/20/2012 07:56 AM, H. Peter Anvin wrote:
> On 07/19/2012 04:52 PM, Alex Shi wrote:
>>
>> Sure, it is a bug, the fix had sent:
>> https://lkml.org/lkml/2012/7/6/350
>>
>
> Could you please re-send that as a clean patch?
>
> -hpa
>
Since, it has not impact for the serial left
On 07/19/2012 04:52 PM, Alex Shi wrote:
>
> Sure, it is a bug, the fix had sent:
> https://lkml.org/lkml/2012/7/6/350
>
Could you please re-send that as a clean patch?
-hpa
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On Thursday, July 19, 2012 4:53 PM, Greg KH wrote:
> On Wed, Jul 18, 2012 at 06:23:20PM -0700, H Hartley Sweeten wrote:
>> All the comedi pci drivers currently store a pointer to the pci_dev
>> in their private data. We can use the 'struct device *hw_dev' variable
>> in the comedi_device struct
On Thursday, July 19, 2012 4:35 PM, gregkh wrote:
> On Thu, Jul 19, 2012 at 06:31:23PM -0500, H Hartley Sweeten wrote:
>> If the comedi pci drivers have the "attach_pci" callback defined, the
>> PCI api does correctly probe the driver. The comedi_pci_auto_config()
>> then passes the pci_dev
On Thu, Jul 19, 2012 at 02:53:01PM +1000, Stephen Rothwell wrote:
> Hi Greg,
>
> Today's linux-next merge of the staging tree got a conflict in
> drivers/staging/Kconfig between commit d0146d396bfa ("tcm_vhost: Initial
> merge for vhost level target fabric driver") from the target-merge tree
>
On Wed, Jul 18, 2012 at 06:23:20PM -0700, H Hartley Sweeten wrote:
> All the comedi pci drivers currently store a pointer to the pci_dev
> in their private data. We can use the 'struct device *hw_dev' variable
> in the comedi_device struct instead and introduce a wrapper for
> to_pci_dev() to
>> +static inline void flush_tlb_mm_range(struct vm_area_struct *vma,
>> + unsigned long start, unsigned long end, unsigned long vmflag)
>> +{
>> +if (vma->vm_mm == current->active_mm)
>> +__flush_tlb();
>> +}
>
> There's a problem with this in one of my randconfig tests.
On Thu, 2012-07-19 at 16:32 -0600, Shuah Khan wrote:
> On Thu, 2012-07-19 at 14:51 -0600, Toshi Kani wrote:
>
> > If your concern is actually a performance bottleneck in acpi_get_name()
> > you found in the code, you should report it to the ACPI CA team.
>
> I have tried my best to get you to
We can dereference 'cxt->cprz' if console and dump logging are disabled
(which is unlikely, but still possible to do). This patch fixes the issue
by changing the code so that we don't dereference przs at all, we can
just calculate bufsize from console_size and record_size values.
Plus, while at
> If you are concerned about multiple OOPS case, I think an user app which logs
> from /dev/pstore to /var/log should be developed.
Agreed - we need an app/daemon to do this.
> Once it is developed, we don't need to care about multiple oops case and the
> appropriate number is two.
Only if
> > OK, please include those questions/answers in the git commit and
> > repost.
I seem to be missing the rest of the patches. I see the drivers/xen/events also
has the xen_init_IRQ_arm... is there a git tree with the base patches?
>
> ---
>
> xen/arm: enable evtchn irqs
>
> On ARM Linux irqs
On Thu, Jul 19, 2012 at 06:31:23PM -0500, H Hartley Sweeten wrote:
> On Thursday, July 19, 2012 4:17 PM, gregkh wrote:
> > On Thu, Jul 19, 2012 at 12:12:02PM -0500, H Hartley Sweeten wrote:
> >> I was planning on making a comedi_find_pci_dev() function that the
> >> drivers could call with a
Hi,
I noticed in a multi-process parallel files reading benchmark I ran on a
8 socket machine, throughput slowed down by a factor of 8 when I ran
the benchmark within a cgroup container. I traced the problem to the
following code path (see below) when we are trying to reclaim memory
from file
On Thursday, July 19, 2012 4:17 PM, gregkh wrote:
> On Thu, Jul 19, 2012 at 12:12:02PM -0500, H Hartley Sweeten wrote:
>> I was planning on making a comedi_find_pci_dev() function that the
>> drivers could call with a "match" callback. This would allow a common
>> function for most of the
On Thu, Jul 19, 2012 at 10:30:38PM +, KY Srinivasan wrote:
> > > As you know, this ID has been in use for a long time now. While the
> > > hypervisor
> > > does not interpret the guest ID that is registered, I am not sure what
> > dependencies
> > > there might be on this value.
> >
> >
On 07/13/2012 11:54 AM, Dave Jones wrote:
> On Fri, Jul 13, 2012 at 08:47:38PM +0200, Thomas Gleixner wrote:
> > On Fri, 13 Jul 2012, Dave Jones wrote:
> >
> > > Looks like calling futex() with garbage makes things unhappy.
> >
> > WARN_ON(!_state);
> >
Hi Dan,
On Thu, Jul 19, 2012 at 05:28:56PM +0300, Dan Carpenter wrote:
> The patch a694d1b5916a: "pstore/ram: Add ftrace messages handling"
> from Jul 9, 2012, leads to the following Smatch complaint:
A nice tool. The homepage of Smatch doesn't explicitly say that, so
I have to ask: is it a
On 07/19/2012 05:30 PM, KY Srinivasan wrote:
-Original Message-
From: Greg KH (gre...@linuxfoundation.org)
[mailto:gre...@linuxfoundation.org]
Sent: Thursday, July 19, 2012 6:02 PM
To: KY Srinivasan
Cc: Paolo Bonzini; de...@linuxdriverproject.org; linux-kernel@vger.kernel.org;
On Thu, Jul 19, 2012 at 12:12:02PM -0500, H Hartley Sweeten wrote:
> On Thursday, July 19, 2012 2:38 AM, Ian Abbott wrote:
> > On 2012-07-19 02:30, H Hartley Sweeten wrote:
> >> Use pci_is_enabled() in the "find pci device" function to determine if
> >> the found pci device is not in use and move
>
> I think that 3 or 4 logs should be plenty to cover almost all situations. E.g.
> with 3 logs you could capture 2 OOPS (and perhaps miss some other OOPS) and
> then get the final panic that kills the system. Messier
> crashes are of course possible ... but that would give lots of clues on
On 07/19/2012 04:04 PM, Steven Rostedt wrote:
> On Thu, 2012-07-19 at 15:53 -0700, H. Peter Anvin wrote:
>
>> lea is not typically faster than add, but in the case of Atom, it is
>> done in an earlier pipeline stage (AGU instead of ALU) which means lea
>> is faster if its inputs are already
On Thu, 2012-07-19 at 15:53 -0700, H. Peter Anvin wrote:
> lea is not typically faster than add, but in the case of Atom, it is
> done in an earlier pipeline stage (AGU instead of ALU) which means lea
> is faster if its inputs are already available as address expressions and
> is consumed by
On Wed, Jul 18, 2012 at 10:53:09AM +0200, Claudio Scordino wrote:
> Il 06/07/2012 19:41, Greg KH ha scritto:
> >On Wed, Jun 27, 2012 at 06:01:39PM +0200, Claudio Scordino wrote:
> >>Hi Olav,
> >>
> >>please find below a patch for the isp1362-hcd.c driver to always
> >>save the message in case
On Thu, Jul 19, 2012 at 10:10:27PM +0100, jan.bannis...@gmail.com wrote:
> From: Jan Bannister
>
> Fixed a coding style issue
NAK, because I'm sick and tired of the pompous commit messages. I'm fine
with adding those spaces. However, I _do_ have a lot against the commit
messages like that.
On 07/19/2012 05:58 AM, Steven Rostedt wrote:
>>
>> also, because lea is faster than add (and doesn't even modify flags), I
>> changed the last part to use lea instead of addl.
>
> Now I'm told that this is not always the case (at least not for Atom),
> so I reverted this part and put back the
On Thu, 2012-07-19 at 18:35 -0400, Josh Boyer wrote:
> > >2... yeah. I don't really know if that is going to pan out, but I am
> > >ever hopeful. I'd be mostly concerned with people that are coding
> > >userspace applications using every whiz-bang kernel feature. Or not
> > >paying attention
Thomas Abraham wrote:
>
> On 19 July 2012 20:58, Jaehoon Chung wrote:
> > Hi Thomas,
> >
> > I think not good that added the samsung specific code into dw_mmc-
> pltfm.c
> > How about separating to dw-mmc-exynos.c?
>
> I am not sure of this. The only samsung specific code in
> dw_mmc-pltfm.c
On 07/19/2012 11:48 PM, Rafael J. Wysocki wrote:
On Thursday, July 19, 2012, Carsten Emde wrote:
There are two cpuidle governors ladder and menu. While the ladder
governor is always available, if CONFIG_CPU_IDLE is selected, the
menu governor additionally requires CONFIG_NO_HZ.
A particular C
1 - 100 of 952 matches
Mail list logo
