On Sun, Nov 10, 2013 at 12:35 AM, Dan Carpenter
wrote:
> I sent a patch to fix some bitwise AND tests but I guess I missed some.
> Sorry about that.
>
> Signed-off-by: Dan Carpenter
Patch applied for fixes, thanks!
Yours,
Linus Walleij
--
To unsubscribe from this list: send the line
On Tue, Nov 19, 2013 at 2:43 AM, Stephen Rothwell wrote:
> Today's linux-next merge of the gpio tree got a conflict in
> drivers/gpio/gpiolib.c between commit 7b1998116bbb ("ACPI / driver core:
> Store an ACPI device pointer in struct acpi_dev_node") from the pm tree
> and commit f760f1967ee8
On 19.11.2013 00:19, Stephen Warren wrote:
> On 11/18/2013 10:25 AM, Michal Marek wrote:
>> MFD_AS3722 can only be builtin, so it needs I2C builtin as well.
>> With I2C=m, we get:
>>
>> drivers/mfd/as3722.c:372: undefined reference to `devm_regmap_init_i2c'
>> drivers/built-in.o: In function
We are happy to announce the Jailhouse project, now also to a broader
community!
Jailhouse is a partitioning hypervisor that can create asymmetric
multiprocessing (AMP) setups on Linux-based systems. That means it runs
bare-metal applications or non-Linux OSes aside a standard Linux kernel
on one
* H. Peter Anvin wrote:
> On 11/18/2013 09:50 AM, Johannes Löthberg wrote:
> > Replace all mixed indentation with tabs
> >
> > Signed-off-by: Johannes Löthberg
>
> NAK. Not worth the churn in the absence of other changes.
Yes.
If a20.c was cleaned up altogether, that might be a more
When IPC_RMID races with other shm operations there's potential for
use-after-free of the shm object's associated file (shm_file).
Here's the race before this patch:
TASK 1 TASK 2
-- --
shm_rmid()
ipc_lock_object()
* Davidlohr Bueso wrote:
> On Wed, 2013-11-13 at 09:25 -0800, tip-bot for Peter Zijlstra wrote:
> > Commit-ID: 911b2898b3c9fe0048e9485ad1629ed4fce330fd
> > Gitweb:
> > http://git.kernel.org/tip/911b2898b3c9fe0048e9485ad1629ed4fce330fd
> > Author: Peter Zijlstra
> > AuthorDate: Mon,
On lun, 2013-11-18 at 16:58 -0500, Elena Ufimtseva wrote:
> Xen vnuma introduction.
>
> The patchset introduces vnuma to paravirtualized Xen guests
> runnning as domU.
> Xen subop hypercall is used to retreive vnuma topology information.
> Bases on the retreived topology from Xen, NUMA number of
On lun, 2013-11-18 at 15:25 -0500, Elena Ufimtseva wrote:
> Signed-off-by: Elena Ufimtseva
> diff --git a/arch/x86/xen/Makefile b/arch/x86/xen/Makefile
> index 96ab2c0..de9deab 100644
> --- a/arch/x86/xen/Makefile
> +++ b/arch/x86/xen/Makefile
> @@ -13,7 +13,7 @@ CFLAGS_mmu.o
The f2fs has three bio types, NODE, DATA, and META, and manages some data
structures per each bio types.
The codes are a little bit messy, thus, this patch introduces a bio array
which groups individual data structures as follows.
struct f2fs_bio_info {
struct bio *bio;/*
The f2fs manages an extent cache to search a number of consecutive data blocks
very quickly.
However it conducts unnecessary cache operations if the file is highly
fragmented with no valid extent cache.
In such the case, we don't need to handle the extent cache, but just can disable
the cache
* Jonathan Corbet wrote:
> On Tue, 19 Nov 2013 00:42:09 +0100
> Peter Zijlstra wrote:
>
> > I briefly talked to Thomas about this earlier today and we need to
> > fix this at a lower level -- the quick 'n dirty solution is to add
> > 1 jiffy down in the timer-wheel when we enqueue these
* Vince Weaver wrote:
> On Mon, 18 Nov 2013, One Thousand Gnomes wrote:
>
> > On Mon, 18 Nov 2013 11:41:22 -0500 (EST)
> > Vince Weaver wrote:
> >
> > > On Mon, 18 Nov 2013, Peter Zijlstra wrote:
> > >
> > > > On Fri, Nov 15, 2013 at 01:04:23PM -0500, Vince Weaver wrote:
> > > > >
> > > >
* Adam Williamson wrote:
> On Fri, 2013-11-01 at 15:02 +0100, Joerg Roedel wrote:
> > On Sun, Oct 27, 2013 at 12:06:29AM -0700, Adam Williamson wrote:
> > > On Sat, 2013-10-26 at 11:15 +0200, Ingo Molnar wrote:
> > > > CONFIG_IRQ_REMAP=y
> > >
> > > Agh, sorry - I had this down in my mind as
* David Ahern wrote:
> This is mmap'ed output, not the ring buffers or its stack. As the
> output file grows, new pages are needed and those are allocated on
> access via page faults. The ftruncate only extends the file size, it
> does not allocate pages at that time.
Hm, doesn't
* Namhyung Kim wrote:
> > Well, with 1 khz sampling of a single threaded workload it's 8MB
> > per second - that's 80 MB for 10 seconds profiling - not the end
> > of the world.
>
> We now use 4 khz sampling frequency by default, just FYI. :)
Yes, but if someone samples with 1 khz that's
* Andi Kleen wrote:
> From: Andi Kleen
>
> Properly patching running code ("cross modification")
> is a quite complicated business on x86.
>
> The CPU has specific rules that need to be followed, including
> multiple global barriers.
>
> Self modifying code is getting more popular, so it's
Hi,
2013-11-19 (화), 13:25 +0800, Chao Yu:
> Hi
>
> > -Original Message-
> > From: Jaegeuk Kim [mailto:jaegeuk@samsung.com]
> > Sent: Monday, November 18, 2013 5:12 PM
> > Cc: linux-fsde...@vger.kernel.org; linux-kernel@vger.kernel.org;
> > linux-f2fs-de...@lists.sourceforge.net
> >
For Exynos4 and Exynos5 SoCs from Samsung the i2c clock is based
on a fixed 66 MHz peripheral clock, and therefore is completely
independent of the cpu frequency.
Thus, registering for a CPU freq notifier is very wasteful.
This patch modifes the code such that, i2c bus registers to
On Mon, Nov 18, 2013 at 10:38:17AM -0700, Bjorn Helgaas wrote:
> [+cc Myron, Amos, Thomas, Ben]
>
> On Mon, Nov 18, 2013 at 2:40 AM, Adam Lee wrote:
> > This patch adds the PCI_EXP_FLAGS_SLOT check back before setting
> > hotplug bridge, which is omitted by an API switching commit,
> >
On Tue, 19 Nov 2013 02:49:38 +0100 Sebastian Reichel wrote:
> Hi,
>
> On Tue, Nov 19, 2013 at 11:30:13AM +1100, NeilBrown wrote:
> > No new configuration, just a 'compatible' string and
> > documentation.
>
> itg3200 looks like a candidate for the list of trivial i2c
> devices [0] to me.
>
>
commit 46a310b ([CPUFREQ] Don't set stat->last_index to -1 if the pol->cur has
incorrect value.) tries to handle case where policy->cur does not match any
entry in freq_table.
As indicated in the above commit, the exact match search of freq_table_get index
will return a -1 which is stored in
This patch adds vfio iommu support for Freescale IOMMU (PAMU -
Peripheral Access Management Unit).
The Freescale PAMU is an aperture-based IOMMU with the following
characteristics. Each device has an entry in a table in memory
describing the iova->phys mapping. The mapping has:
-an overall
On Mon, 18 Nov 2013, Linus Torvalds wrote:
> On Mon, Nov 18, 2013 at 3:30 PM, James Morris wrote:
> > On Mon, 18 Nov 2013, Josh Boyer wrote:
> >>
> >> Unless I'm missing something, I don't think this has landed in Linus'
> >> tree yet. Linus, did this pull request get NAKed or fall through the
On 11/12/2013 2:51 PM, srinivas.kandaga...@st.com wrote:
From: Srinivas Kandagatla
Hi All,
This patch series adds Ethernet support to STi series SOCs STiH415 and STiH416.
STi SOC series integrates dwmac IP from synopsis, however there is a hardware
glue on top of this standard IP, this glue
Hi
> -Original Message-
> From: Jaegeuk Kim [mailto:jaegeuk@samsung.com]
> Sent: Monday, November 18, 2013 5:12 PM
> Cc: linux-fsde...@vger.kernel.org; linux-kernel@vger.kernel.org;
> linux-f2fs-de...@lists.sourceforge.net
> Subject: [f2fs-dev] [PATCH 1/2] f2fs: clean up the
In Aperture type of IOMMU (like FSL PAMU), VFIO-iommu system need to know
the MSI region to map its window in h/w. This patch just defines the
required weak functions only and will be used by followup patches.
Signed-off-by: Bharat Bhushan
---
v1->v2
- Added description on "struct msi_region"
The FSL MSI will provide the interface to get:
- Number of MSI regions (which is number of MSI banks for powerpc)
- Get the region address range: Physical page which have the
address/addresses used for generating MSI interrupt
and size of the page.
These are required to create IOMMU
On 11/18/2013 12:30 PM, srinivas.kandaga...@st.com wrote:
From: Srinivas Kandagatla
Hi Peppe,
During PM_SUSPEND_FREEZE testing, I have noticed that PM support in STMMAC is
partly broken. I had to re-arrange the code to do PM correctly. There were lot
of things I did not like personally and
This patch extend the interface to arch specific code for setting
msi iova address for a msi page. Machine specific code is not yet
implemented.
Signed-off-by: Bharat Bhushan
---
v2
- new patch
arch/powerpc/include/asm/machdep.h |2 ++
arch/powerpc/kernel/msi.c | 10 ++
Now we Keep track of devices which have msi page mapping to specific
iova page for all msi bank. When composing MSI address and data then
this list will be traversed. If device found in the list then use
configured iova page otherwise iova page will be taken as before.
Signed-off-by: Bharat
On 11/18/2013 04:27 PM, Andi Kleen wrote:
>
> Proposed man page:
>
> NAME
> text_poke - Safely modify running instructions (x86)
>
> SYNOPSYS
> int text_poke(void *addr, const void *opcode, size_t len,
> void (*handler)(void), int timeout);
>
> DESCRIPTION
>
Some function defined in vfio_iommu_type1.c are generic (not specific
or type1 iommu) and we want to use these for FSL IOMMU (PAMU) and
going forward in iommu-none driver.
So I have created a new file naming vfio_iommu_common.c and moved some
of generic functions into this file.
I Agree (with
This patch defines an interface by which a msi page
can be mapped to a specific iova page.
This is a requirement in aperture type of IOMMUs (like Freescale PAMU),
where we map msi iova page just after guest memory iova address.
Signed-off-by: Bharat Bhushan
---
v2
- new patch
So by now we have defined all the interfaces for getting the msi region,
this patch expose the interface to linux subsystem. These will be used by
vfio subsystem for setting up iommu for MSI interrupt of direct assignment
devices.
Signed-off-by: Bharat Bhushan
---
v1->v2
- None
This patch adds the interface to get the msi region information from arch
specific code. The machine spicific code is not yet defined.
Signed-off-by: Bharat Bhushan
---
v1->v2
- None
arch/powerpc/include/asm/machdep.h |8
arch/powerpc/kernel/msi.c | 18
From: Bharat Bhushan
PAMU (FSL IOMMU) has a concept of primary window and subwindows.
Primary window corresponds to the complete guest iova address space
(including MSI space), with respect to IOMMU_API this is termed as
geometry. IOVA Base of subwindow is determined from the number of
On 11/18/2013 09:18 AM, Ivan Khoronzhuk wrote:
The keystone arch use the same IP watchdog, so add "ti,keystone-wdt"
compatible and correct identity.
The Keystone arch is using clocks in DT and source clock for watchdog
has to be specified, so add this to binding.
Signed-off-by: Ivan Khoronzhuk
On 11/18/2013 09:18 AM, Ivan Khoronzhuk wrote:
Since Davinci WDT has been switched to use WDT core, it became able
to support timeout-sec property, so add it to it's binding description.
Signed-off-by: Ivan Khoronzhuk
Acked-by: Santosh Shilimkar
Acked-by: Guenter Roeck
---
Need include generic "vga.h", or can not pass compiling with
allmodconfig, the related error:
CC [M] drivers/gpu/drm/drm_irq.o
In file included from include/linux/vgaarb.h:34:0,
from drivers/gpu/drm/drm_irq.c:42:
include/video/vga.h:22:21: fatal error: asm/vga.h: No
On 11/18/2013 09:18 AM, Ivan Khoronzhuk wrote:
Currently, the davinci watchdog can be read while counting,
so we can add ability to report the remaining time before
the system will reboot.
Signed-off-by: Ivan Khoronzhuk
Acked-by: Santosh Shilimkar
Reviewed-by: Guenter Roeck
---
On 11/18/2013 09:18 AM, Ivan Khoronzhuk wrote:
To reduce code duplicate and increase code readability use WDT core
code to handle WDT interface.
Remove io_lock as the WDT core uses mutex to lock each wdt device.
Remove wdt_state as the WDT core track state with its own variable.
The
On 11/18/2013 05:24 PM, Markus Mayer wrote:
This commit enables the watchdog driver for the BCM281xx family of SoCs.
Signed-off-by: Markus Mayer
Reviewed-by: Matt Porter
Acked-by: Guenter Roeck
---
arch/arm/configs/bcm_defconfig |3 +++
1 file changed, 3 insertions(+)
diff --git
On 11/18/2013 05:24 PM, Markus Mayer wrote:
This commit adds support for the watchdog timer used on the BCM281xx
family of SoCs.
Signed-off-by: Markus Mayer
Reviewed-by: Matt Porter
---
drivers/watchdog/Kconfig| 22 +++
drivers/watchdog/Makefile |1 +
Hi
> -Original Message-
> From: Jaegeuk Kim [mailto:jaegeuk@samsung.com]
> Sent: Tuesday, November 19, 2013 11:36 AM
> To: Chao Yu
> Cc: linux-fsde...@vger.kernel.org; linux-kernel@vger.kernel.org;
> linux-f2fs-de...@lists.sourceforge.net
> Subject: Re: [f2fs-dev] [PATCH] f2fs: split
When HAS_DMA, and also need use generic implementation, HAVE_DMA_ATTR
must be enabled, or can not pass compiling with allmodconfig, the
related error:
CC [M] drivers/ata/libata-core.o
drivers/ata/libata-core.c: In function 'ata_sg_clean':
drivers/ata/libata-core.c:4598:3: error: implicit
On 11/19/2013 08:48 AM, Stephen Warren wrote:
On 11/18/2013 04:43 AM, Thierry Reding wrote:
On Mon, Nov 18, 2013 at 07:40:47PM +0900, Alexandre Courbot wrote:
FUSE clock is enabled by most bootloaders, but we cannot expect
it to be on in all contexts (e.g. kexec).
This patch adds a FUSE
Hi Guenter,
On Mon, 18 Nov 2013 20:08:54 -0800 Guenter Roeck wrote:
>
> > Merging h8300-remove/h8300-remove (b400126add8f CREDITS: Add Yoshinori Sato
> > for h8300)
>
> This tree has been merged upstream and is no longer needed.
Thanks, I will remove it tomorrow.
--
Cheers,
Stephen Rothwell
On 11/16/2013 10:44 PM, Linus Torvalds wrote:
> So this doesn't do the 32-bit truncation in the error path of the generic
> string copy. Oversight?
>
>Linus
Hi Linus,
Do you have a preference:
1. Considering the 32-bit truncation incidental (take it or leave it);
2. Require the 32-bit
On 11/18/2013 08:43 PM, Thierry Reding wrote:
* PGP Signed by an unknown key
On Mon, Nov 18, 2013 at 07:40:47PM +0900, Alexandre Courbot wrote:
FUSE clock is enabled by most bootloaders, but we cannot expect it to be
on in all contexts (e.g. kexec).
This patch adds a FUSE clkdev to all Tegra
Sorry for the late reply.
The presence of the unfair option as default is largely due to fixing the
recursive read lock in interrupt handler problem. You are right that it is no
longer a valid reason now.
An unfair lock may have a better performance characteristics, especially for a
highly
On Tue, Nov 19, 2013 at 2:38 AM, Steven Rostedt wrote:
> When Jiri Olsa was writing a function callback for
> scsi_trace_parse_cdb(), he thought that the traceevent library had a
> bug in it because he was getting this error:
>
> Error: expected ')' but read ','
> Error: expected ')' but read
Remove CONFIG_USE_GENERIC_SMP_HELPERS left by commit
0a06ff06("kernel: remove CONFIG_USE_GENERIC_SMP_HELPERS").
Cc: Christoph Hellwig
Cc: Andrew Morton
Signed-off-by: Yuanhan Liu
---
drivers/block/null_blk.c |8
net/Kconfig |4 ++--
2 files changed, 6
On Tue, Nov 19, 2013 at 02:39:54PM +1100, Stephen Rothwell wrote:
> Hi all,
>
Hi Stephen,
> Merging h8300-remove/h8300-remove (b400126add8f CREDITS: Add Yoshinori Sato
> for h8300)
This tree has been merged upstream and is no longer needed.
Thanks,
Guenter
--
To unsubscribe from this list:
On 19 November 2013 07:51, Shawn Guo wrote:
> No, I did not say that. IMO, when cpufreq-cpu0 sees a mismatch, it has
> no way to know or assume which one is correct and which is incorrect.
> The best thing it can do is to fail out without changing anything about
> running frequency and voltage.
Hi all,
Please do *not* add any v3.14 material to linux-next until after
v3.13-rc1 is released.
Changes since 20131118:
The nfs tree lost its build failure but gained another for which I
reverted a commit.
The gpio tree gained a conflict against the pm tree
Hi,
I think we don't need to make two patches for this.
How about this?
>From 71c27f78e72d680edcd7b1c0917842343044653c Mon Sep 17 00:00:00 2001
From: Jaegeuk Kim
Date: Mon, 18 Nov 2013 17:16:17 +0900
Subject: [PATCH] f2fs: use sbi->write_mutex for write bios
This patch removes an unnecessary
On Mon, Nov 18, 2013 at 7:28 PM, Al Viro wrote:
>
> BTW, I've several old commits that didn't go into the first pile (e.g.
> taking read_seqbegin_or_lock() and friends from fs/dcache.c into
> linux/seqlock.h, where they obviously belong, etc.) and several regression
> fixes; are you OK with pull
On Mon, Nov 18, 2013 at 07:13:54PM -0800, Linus Torvalds wrote:
>
>
> On Tue, 19 Nov 2013, Al Viro wrote:
> >
> > seq_file: always clear m->count when we free m->buf
>
> Ok, applied.
>
> What do you think about then just abstracing out that now common sequence
> of re-allocating a larger
The maximum packet number which a tx aggregation buffer could contain
is the buffer size / (packet size + descriptor size).
If the tx buffer is empty and the tx queue length is more than the
maximum value which is defined above, stop the tx queue. Wake the tx
queue after any queued packet is
The data from the hardware should be little endian. Correct the
declaration.
Signed-off-by: Hayes Wang
---
drivers/net/usb/r8152.c | 18 +-
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/drivers/net/usb/r8152.c b/drivers/net/usb/r8152.c
index 0ac2b53..fb35e6e
Remove the code for sending the packet in the rtl8152_start_xmit().
Let rtl8152_start_xmit() to queue the packet only, and schedule a
tasklet to send the queued packets. This simplify the code and make
sure all the packet would be sent by the original order.
Signed-off-by: Hayes Wang
---
For the patch #1, I modify the type of the variable "pkt_len" from "unsigned"
to "unsigned int".
Hayes Wang (4):
r8152: fix tx/rx memory overflow
r8152: modify the tx flow
r8152: support stopping/waking tx queue
r8152: fix incorrect type in assignment
drivers/net/usb/r8152.c | 109
The tx/rx would access the memory which is out of the desired range.
Modify the method of checking the end of the memory to avoid it.
For r8152_tx_agg_fill(), the variable remain may become negative.
However, the declaration is unsigned, so the while loop wouldn't
break when reaching the end of
Hi,
2013-11-19 (화), 09:43 +0800, Chao Yu:
> All DATA/NODE/META bio buffers in superblock is protected by
> 'sbi->write_mutex', but each bio buffer area is independent, So we
> should split write_mutex to three for DATA/NODE/META.
Agreed, one comment below though.
Anyway I'll send v2.
Thanks,
On Wed, 2013-11-13 at 09:25 -0800, tip-bot for Peter Zijlstra wrote:
> Commit-ID: 911b2898b3c9fe0048e9485ad1629ed4fce330fd
> Gitweb: http://git.kernel.org/tip/911b2898b3c9fe0048e9485ad1629ed4fce330fd
> Author: Peter Zijlstra
> AuthorDate: Mon, 11 Nov 2013 18:21:56 +0100
> Committer:
isimatu.yasu...@jp.fujitsu.com writes:
> Hi Matt,
>
> Sorry for late the reply.
>
>
> (2013/11/11 19:54), Matt Fleming wrote:
>> On Mon, 11 Nov, at 05:52:59PM, Yasuaki Ishimatsu wrote:
>>> Hi Matt,
>>>
>>> I uses FUJITSU's x86 box.
>>> This does not become bricked even if I use all efi variable
On Tue, 19 Nov 2013, Al Viro wrote:
>
> seq_file: always clear m->count when we free m->buf
Ok, applied.
What do you think about then just abstracing out that now common sequence
of re-allocating a larger buffer, while clearing m->count?
IOW, something like the appended..
On Mon, Nov 18, 2013 at 10:37:13AM -0800, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.12.1 release.
> There are 19 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me
On Mon, Nov 18, 2013 at 10:40:29AM -0800, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.11.9 release.
> There are 25 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me
Need add __delay() implementation, or can not pass allmodconfig in
next-20131118 tree.
The related error:
CC kernel/locking/spinlock_debug.o
kernel/locking/spinlock_debug.c: In function '__spin_lock_debug':
kernel/locking/spinlock_debug.c:114:3: error: implicit declaration
On Mon, Nov 18, 2013 at 10:42:10AM -0800, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.10.20 release.
> There are 24 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me
On Mon, Nov 18, 2013 at 10:41:33AM -0800, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.4.70 release.
> There are 12 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me
Hi Matt,
Sorry for late the reply.
(2013/11/11 19:54), Matt Fleming wrote:
On Mon, 11 Nov, at 05:52:59PM, Yasuaki Ishimatsu wrote:
Hi Matt,
I uses FUJITSU's x86 box.
This does not become bricked even if I use all efi variable storage.
Thus I want a way to not need to specify
On Mon, Nov 18, 2013 at 5:32 PM, H. Peter Anvin wrote:
> On 11/15/2013 10:30 AM, Vivek Goyal wrote:
>>
>> And IOMMU support is very flaky with kdump. And IOMMU's can be turned
>> off at command line. And that would force one to remove crahkernel_low=0.
>> So change of one command line option
On 11/18/2013 08:58 PM, Catalin Marinas wrote:
On Mon, Nov 18, 2013 at 03:05:59AM +, Alex Courbot wrote:
On 11/18/2013 12:59 AM, Catalin Marinas wrote:
On 17 November 2013 08:49, Alexandre Courbot wrote:
The ARM tree includes a firmware_ops interface that is designed to
implement support
> Thanks Tejun and Hugh. Sorry for my late entry in getting around to
> testing this fix. On the surface it sounds correct however I'd like to
> test this on top of 3.10.* since that is what we'll likely be running.
> I've tried to apply Hugh's patch above on top of 3.10.19 but it
> appears there
When Jiri Olsa was writing a function callback for
scsi_trace_parse_cdb(), he thought that the traceevent library had a
bug in it because he was getting this error:
Error: expected ')' but read ','
Error: expected ')' but read ','
Error: expected ')' but read ','
Error: expected ')' but
On Tue, Nov 19, 2013 at 2:33 AM, David Ahern wrote:
> On 11/18/13, 7:30 PM, Namhyung Kim wrote:
>>
>> On Mon, 18 Nov 2013 19:17:37 -0700, David Ahern wrote:
>>>
>>> On 11/18/13, 7:13 PM, Namhyung Kim wrote:
I think it should be
perf record -e cycles -F 4000 -e faults -c 1
On 11/18/13, 7:30 PM, Namhyung Kim wrote:
On Mon, 18 Nov 2013 19:17:37 -0700, David Ahern wrote:
On 11/18/13, 7:13 PM, Namhyung Kim wrote:
I think it should be
perf record -e cycles -F 4000 -e faults -c 1 --call-graph dwarf,8192 -a --
sleep 1
(at least to generate the feedback spiral
David Miller [mailto:da...@davemloft.net]
> Sent: Saturday, November 16, 2013 6:40 AM
> To: Hayeswang
> Cc: net...@vger.kernel.org; nic_swsd;
> linux-kernel@vger.kernel.org; linux-...@vger.kernel.org
> Subject: Re: [PATCH net v3 1/4] r8152: fix tx/rx memory overflow
>
> From: Hayes Wang
>
On 11/18/2013 04:27 PM, Andi Kleen wrote:
> From: Andi Kleen
>
> Properly patching running code ("cross modification")
> is a quite complicated business on x86.
>
> The CPU has specific rules that need to be followed, including
> multiple global barriers.
>
> Self modifying code is getting
On Tue, 19 Nov 2013 11:23:56 +0900
Namhyung Kim wrote:
> > arg->type = PRINT_FUNC;
> > @@ -2708,15 +2707,19 @@ process_func_handler(struct event_format *event,
> > struct pevent_function_handler
> > }
> >
> > type = process_arg(event, farg, );
> > - if
On Mon, 18 Nov 2013 19:17:37 -0700, David Ahern wrote:
> On 11/18/13, 7:13 PM, Namhyung Kim wrote:
>> I think it should be
>>
>>perf record -e cycles -F 4000 -e faults -c 1 --call-graph dwarf,8192 -a
>> -- sleep 1
>>
>> (at least to generate the feedback spiral more efficiently..)
>
> you
On 11/03/2013 04:02 AM, Andreas Werner wrote:
> Revision 2:
> added comment in code.
>
> This patch adds the Write-through memory type in combination with mtrr.
> If you call ioremap_cache to request cachable memory (write-back) the
> function tries to set the PAT to write-back only if the
Hi Steven,
On Mon, 18 Nov 2013 19:11:31 -0500, Steven Rostedt wrote:
> When Jiri Olsa was writing a function callback for
> scsi_trace_parse_cdb(), he thought that the traceevent library had a
> bug in it because he was getting this error:
>
> Error: expected ')' but read ','
> Error:
On 11/18/2013 09:50 AM, Johannes Löthberg wrote:
> Replace all mixed indentation with tabs
>
> Signed-off-by: Johannes Löthberg
NAK. Not worth the churn in the absence of other changes.
-hpa
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
Hi Linus:
Here is a resend of crypto the update for 3.13:
* Made x86 ablk_helper generic for ARM.
* Phase out chainiv in favour of eseqiv (affects IPsec).
* Fixed aes-cbc IV corruption on s390.
* Added constant-time crypto_memneq which replaces memcmp.
* Fixed aes-ctr in omap-aes.
* Added OMAP3
On Mon, Nov 18, 2013 at 10:41:36AM -0600, Nishanth Menon wrote:
> In the case of mismatch, to consider that device tree may be wrong in
> driver is also to assume that hardware was always configured correctly
> and we assume description is the flawed data.
No, I did not say that. IMO, when
On 11/18/13, 7:13 PM, Namhyung Kim wrote:
I think it should be
perf record -e cycles -F 4000 -e faults -c 1 --call-graph dwarf,8192 -a --
sleep 1
(at least to generate the feedback spiral more efficiently..)
you don't need the cycles. faults by itself works. Each event contains >
2
On Mon, Nov 18, 2013 at 10:51:30PM +0100, Pali Rohár wrote:
> On Wednesday 16 October 2013 14:57:34 Herbert Xu wrote:
> > On Tue, Oct 08, 2013 at 12:04:09PM -0700, Tony Lindgren wrote:
> > > * Pali Rohár [130920 06:33]:
> > > > This driver provides kernel-side support for the Random
> > > >
On Mon, 18 Nov 2013 17:34:49 -0700, David Ahern wrote:
> On 11/18/13, 5:24 PM, Namhyung Kim wrote:
> What now? Can we add the mmap path as an option?
I'd say an option is always a possibility, but someone please try
what happens if you use stupid large events (dwarf stack
Hello Phillip,
Sorry for late response.
On Thu, Nov 14, 2013 at 05:04:36PM +, Phillip Lougher wrote:
> CCing Junjiro Okijima and Stephen Hemminger
>
> On 08/11/13 02:42, Minchan Kim wrote:
> >
> >Hello Phillip,
> >
> >On Thu, Nov 07, 2013 at 08:24:22PM +, Phillip Lougher wrote:
> >>Add
On Mon, 18 Nov 2013 17:34:49 -0700, David Ahern wrote:
> On 11/18/13, 5:24 PM, Namhyung Kim wrote:
> What now? Can we add the mmap path as an option?
I'd say an option is always a possibility, but someone please try
what happens if you use stupid large events (dwarf stack
> The pcie_portdrv .probe() method calls pci_enable_device() once, in
> pcie_port_device_register(), but the .remove() method calls
> pci_disable_device() twice, in pcie_port_device_remove() and in
> pcie_portdrv_remove().
>
> That causes a "disabling already-disabled device" warning when
On Tue, 19 Nov 2013 09:22:54 +0800
Gao feng wrote:
> On 11/19/2013 08:04 AM, Steven Rostedt wrote:
> >
> > I'll start out saying that this email was a complete oops. I only kept
> > it around for reference, as this didn't fix the bug we were seeing, and
> > I used this email to just document
Hi David,
On Tue, Nov 19, 2013 at 12:34 AM, David Ahern wrote:
> On 11/18/13, 5:24 PM, Namhyung Kim wrote:
>
> What now? Can we add the mmap path as an option?
I'd say an option is always a possibility, but someone please try
what happens if you use stupid large
Hi,
On Tue, Nov 19, 2013 at 11:30:13AM +1100, NeilBrown wrote:
> No new configuration, just a 'compatible' string and
> documentation.
itg3200 looks like a candidate for the list of trivial i2c
devices [0] to me.
[0] Documentation/devicetree/bindings/i2c/trivial-devices.txt
-- Sebastian
1 - 100 of 1351 matches
Mail list logo
