From: Minchan Kim
commit f80c0673610e36ae29d63e3297175e22f70dde5f upstream.
Stable note: Not tracked in Bugzilla. THP and compaction disrupt the LRU list
leading to poor reclaim decisions which has a variable performance
impact.
In __zone_reclaim case, we don't want to shrink
commit cc9a6c8776615f9c194ccf0b63a0aa5628235545 upstream.
Stable note: Not tracked in Bugzilla. [get|put]_mems_allowed() is extremely
expensive and severely impacted page allocator performance. This
is part of a series of patches that reduce page allocator overhead.
Changelog
commit b969c4ab9f182a6e1b2a0848be349f99714947b0 upstream.
Stable note: Not tracked in Bugzilla. A fix aimed at preserving page
aging information by reducing LRU list churning had the side-effect
of reducing THP allocation success rates. This was part of a series
to restore
From: Dave Chinner
commit 3567b59aa80ac4417002bf58e35dce5c777d4164 upstream.
Stable note: Not tracked in Bugzilla. This patch reduces excessive
reclaim of slab objects reducing the amount of information that
has to be brought back in from disk. The third and fourth paragram
From: Dimitri Sivanich
commit a1cb2c60ddc98ff4e5246f410558805401ceee67 upstream.
Stable note: Not tracked on Bugzilla. This patch is known to make a big
difference to tmpfs performance on larger machines.
Avoid false sharing of the vm_stat array. This was found to adversely
affect
Hello Anton Vorontsov,
This is a semi-automatic email about new static checker warnings.
The patch a694d1b5916a: "pstore/ram: Add ftrace messages handling"
from Jul 9, 2012, leads to the following Smatch complaint:
fs/pstore/ram.c:423 ramoops_probe()
error: we previously assumed
On Sat, 2012-07-07 at 19:27:12 +, Arnd Bergmann wrote:
> On Saturday 07 July 2012, Olof Johansson wrote:
> > > ARM introduced AArch64 as part of the ARMv8 architecture
> >
> > With the risk of bikeshedding here, but I find the name awkward. How
> > about just naming the arch port arm64
Dear Adam
It did not work (exact same behaviour) with a newer kernel (3.5-rc7).
The problem was the firmware. After a upgrade it works; with older
kernels too. Great thanks and sorry to bother you (all).
Greetings
David
Am 19.07.2012 02:39, schrieb adam radford:
On 7/18/12, stepping stone
On Thu, Jul 19, 2012 at 05:38:03AM -0700, Hugh Dickins wrote:
> On Wed, 18 Jul 2012, Mel Gorman wrote:
>
> > (Sending as RFC as this one is tricky and as it is timing dependent the
> > patch may accidentally be papering over a more fundamental problem. Even
> > if it is not, it may be more heavy
On Thu, Jul 19, 2012 at 09:57:36AM -0400, Vivek Goyal wrote:
> On Thu, Jul 19, 2012 at 11:38:57AM +0200, Kay Sievers wrote:
> > On Wed, Jul 18, 2012 at 7:56 PM, Vivek Goyal wrote:
> > > On Wed, Jul 18, 2012 at 07:27:08PM +0200, Kay Sievers wrote:
> > >> On Wed, Jul 18, 2012 at 7:18 PM, Vivek
On Tue, Jun 12, 2012 at 11:22:02AM -0400, Prarit Bhargava wrote:
> [This seems to have been missed ... sending again]
>
> On a large system with a large number of tasks, the output of
>
> echo t > /proc/sysrq-trigger
>
> can take a long period of time. If this period is greater than the period
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 non-rt kernel?
-- Steve
--
To unsubscribe from this list: send the
On Thu, Jul 19, 2012 at 11:38:57AM +0200, Kay Sievers wrote:
> On Wed, Jul 18, 2012 at 7:56 PM, Vivek Goyal wrote:
> > On Wed, Jul 18, 2012 at 07:27:08PM +0200, Kay Sievers wrote:
> >> On Wed, Jul 18, 2012 at 7:18 PM, Vivek Goyal wrote:
> >>
> >> > Currently I am not exporting log "level" info
On Thu, 2012-07-19 at 09:05 -0400, Steven Rostedt wrote:
> On Thu, 2012-07-19 at 06:00 +0200, Mike Galbraith wrote:
> > On Wed, 2012-07-18 at 18:39 -0400, Steven Rostedt wrote:
> >
> > > Please test the patches too.
> >
> > Your hotplug stress test script made x3550 M3 box fall over. It took a
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 becomes easier if all lines end with \n instead of trying to special
> > case the
On 07/19/2012 09:08 AM, Stephen Rothwell wrote:
> Hi all,
>
> After merging the final tree, today's linux-next build (powerpc allyesconfig)
> failed like this:
>
> drivers/staging/sm7xxfb/sm7xxfb.c: In function 'smtcfb_pci_probe':
> drivers/staging/sm7xxfb/sm7xxfb.c:829:33: error:
Hi Linus,
I'm sending the attached patch directly to you for inclusion in 3.5 as
without it the cx25821 driver will panic on probe.
It looks like this bug has been around since cx25821 was first mainlined,
so it could make sense to consider its inclusion in stable also.
Since Mauro is still on
Dear RT Folks,
I'm pleased to announce the 3.2.23-rt37 stable release.
You can get this release via the git tree at:
git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt.git
Head SHA1: 32a32ba43387e6ad9dd74f38b79ad411c6c1c4e6
Or to build 3.2.23-rt37 directly, the following
On Thu, Jul 19, 2012 at 07:05:51PM +0530, Srivatsa S. Bhat wrote:
> Oh.. ok.. Then this patch is perhaps unnecessary.. Thanks for the
> info!
Probably, if the TLB flushrange set from Alex goes upstream in the next
merge window...
--
Regards/Gruss,
Boris.
--
To unsubscribe from this list: send
On 07/19/2012 07:02 PM, Borislav Petkov wrote:
> On Thu, Jul 19, 2012 at 06:27:33PM +0530, Srivatsa S. Bhat wrote:
>
> [ … ]
>
>> So we are sending an IPI to a cpu which is now offline. Once a cpu is
>> offline,
>> it will no longer respond to IPIs. This explains the softlockup.
>>
>> A cpu in
Linus,
please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/jikos/hid.git upstream-fixes
to receive a final round of changes for HID for 3.5. It's just device ID
additions.
Thanks.
Benjamin Tissoires (1):
HID: hid-multitouch: add support for Zytronic panels
Daniel
Mikulas Patocka writes:
> On Tue, 17 Jul 2012, Jeff Moyer wrote:
>
>> > This is the patch that fixes this crash: it takes a rw-semaphore around
>> > all direct-IO path.
>> >
>> > (note that if someone is concerned about performance, the rw-semaphore
>> > could be made per-cpu --- take it for
On Thu, Jul 19, 2012 at 06:27:33PM +0530, Srivatsa S. Bhat wrote:
[ … ]
> So we are sending an IPI to a cpu which is now offline. Once a cpu is offline,
> it will no longer respond to IPIs. This explains the softlockup.
>
> A cpu in the mm_cpumask could go offline before we send the invalidate
Hi,
> Signed-off-by: Kishon Vijay Abraham I
> ---
> Documentation/devicetree/bindings/usb/omap-usb.txt | 34 -
> drivers/usb/musb/omap2430.c| 55
>
> 2 files changed, 88 insertions(+), 1 deletions(-)
>
> diff --git
>Thanks for your great comments. You are right, it is impossible to get
> correct finger tracking if both fingers are moving. However, we think it
> still worth to have the firmware tracking of the fingers as they could
> perform well for most one-stationary-one-moving cases. This will be
On Thursday 19 July 2012 17:55:10 wei_w...@realsil.com.cn wrote:
> +static int rtsx_pci_transfer_sglist_adma(struct rtsx_pdev *pdev,
> + struct scatterlist *sg, int num_sg, int read, int timeout)
> +{
> + struct completion trans_done;
> + u8 dir;
> + int buf_cnt, i;
> +
On Thu, Jul 19, 2012 at 08:05:42AM -0500, Anthony Liguori wrote:
> Of course, the million dollar question is why would using AIO in the
> kernel be faster than using AIO in userspace?
Actually for me a more important question is how does it compare
with virtio-blk dataplane?
--
MST
--
To
On Thu, Jul 19, 2012 at 08:05:42AM -0500, Anthony Liguori wrote:
> Asias He writes:
>
> > vhost-blk is a in kernel virito-blk device accelerator.
> >
> > This patch is based on Liu Yuan's implementation with various
> > improvements and bug fixes. Notably, this patch makes guest notify and
> >
Asias He writes:
> vhost-blk is a in kernel virito-blk device accelerator.
>
> This patch is based on Liu Yuan's implementation with various
> improvements and bug fixes. Notably, this patch makes guest notify and
> host completion processing in parallel which gives about 60% performance
>
On Thu, 2012-07-19 at 06:00 +0200, Mike Galbraith wrote:
> On Wed, 2012-07-18 at 18:39 -0400, Steven Rostedt wrote:
>
> > Please test the patches too.
>
> Your hotplug stress test script made x3550 M3 box fall over. It took a
> bit, but down she went. 64 core test box fell over quickly, but
Hi Dan,
On Thu, Jul 19, 2012 at 6:20 PM, Dan Carpenter wrote:
> Cleanup means there are no behavior changes. This is a bug fix.
>
Thanks Dan, i will put a proper subject line in commit.
> On Thu, Jul 19, 2012 at 06:00:01PM +0530, Devendra Naga wrote:
>> a) if alloc_hdlcdev fails, we are
Mandeep reports:
We are seeing a softlockup reporting during shutdown. The stack
trace shows us that we are inside default_send_IPI_mask_logical:
BUG: soft lockup - CPU#0 stuck for 11s! [lmt-udev:23605]
Pid: 23605, comm: lmt-udev Tainted: GWC 3.2.7 #1
EIP: 0060:[<8101eec6>] EFLAGS:
On Thu, 2012-07-19 at 08:52 -0400, Steven Rostedt wrote:
>
> GLOBAL(ftrace_regs_call)
> call ftrace_stub
> @@ -1195,8 +1194,8 @@ GLOBAL(ftrace_regs_call)
> popl %es
> popl %fs
> popl %gs
> - addl $8, %esp /* Skip orig_ax and ip */
> - popf
On Thu, Jul 19, 2012 at 11:53:11AM +0200, Willy Tarreau wrote:
> On Tue, Jul 17, 2012 at 05:34:30PM -0700, John Stultz wrote:
> > On 07/17/2012 03:05 PM, John Stultz wrote:
> > >This is the last backport I have ready at this time. I realize there's
> > >still the 2.6.27 tree, but if I recall
On Thu, 19 Jul 2012, Kamezawa Hiroyuki wrote:
> (2012/07/19 18:29), Michal Hocko wrote:
> > On Wed 18-07-12 19:08:54, Wanpeng Li wrote:
> > > use exist interface mem_cgroup_css instead of >css.
> >
> > This interface has been added to enable mem->css outside of
> > mm/memcontrol.c (where we
On Thursday 19 July 2012, Tony Prisk wrote:
> Which brings us back to the original question (and raises another one) - can
> we assume yet that
> 'wmt' will be the vendor-binding for Wondermedia? Also, what are we going to
> use for VIA-based
> SoC's given that VIA is the ticker for VIACOM.
>
On Thu, 2012-07-19 at 11:20 +0900, Masami Hiramatsu wrote:
> (2012/07/19 0:59), Steven Rostedt wrote:
> > On Fri, 2012-07-13 at 14:47 -0400, Steven Rostedt wrote:
> >
> > Masami, can you give your Reviewed-by tag for this version? Or is there
> > something else needing to be fixed?
>
> No, that
Cleanup means there are no behavior changes. This is a bug fix.
On Thu, Jul 19, 2012 at 06:00:01PM +0530, Devendra Naga wrote:
> a) if alloc_hdlcdev fails, we are going into the free_regions,
> and returning out the err (which is 0 by the prev call),
>return -ENOMEM if this function
Set default global limits for backgrounded requests and congestion
threshold considering the tunable maximum request size.
They are calculated using size of fuse_req structure, which is
variable due to it. This patch sets them according to the current
request size unless they are set via
Add an explanation about the sysfs parameter to limit the
maximum read/write request size.
Signed-off-by: Mitsuo Hayasaka
Cc: Rob Landley
Cc: Miklos Szeredi
Cc: Nikolaus Rath
Cc: Liu Yuan
Cc: Has-Wen Nienhuys
---
Documentation/filesystems/fuse.txt | 15 ++-
1 files changed,
From: Vyacheslav Dubeyko
This patch adds omitted comments for different structures in driver
implementation.
[modified so as to comply with kernel-doc data structure comment]
Signed-off-by: Vyacheslav Dubeyko
Signed-off-by: Ryusuke Konishi
---
fs/nilfs2/alloc.h | 14 +++---
Hi Andrew,
Please apply the following two patches and send them upstream at the
upcoming merge window, along with the previous patchset.
These add missing comments on structures in nilfs2.
Thanks,
Ryusuke Konishi
--
Vyacheslav Dubeyko (2):
NILFS2: add omitted comments for structures in
From: Vyacheslav Dubeyko
This patch adds omitted comments for structures in nilfs2_fs.h.
Signed-off-by: Vyacheslav Dubeyko
Signed-off-by: Ryusuke Konishi
---
include/linux/nilfs2_fs.h | 63 -
1 file changed, 39 insertions(+), 24 deletions(-)
Add a max_pages_per_req sysfs paramater to limit the maximum
read/write request size. It can be changed to arbitrary number
between 32 and the nr_pages equivalent to pipe_max_size, and the
32 pages are set by default.
The sysfs parameter control is required, as follows.
* The libfuse should
Make the maximum read/write request size tunable between
32 pages and the number of pages equivalent to pipe_max_size.
The max_read/max_write mount options affect the size. The
32 pages are used by default without these options.
Currently, the maximum read/write request size is limited to
Remove fuse_req_cachep, which was used for fuse request buffer.
It is no longer used since the buffer is allocated dynamically
due to the tunable maximum read/write request size.
Signed-off-by: Mitsuo Hayasaka
Cc: Miklos Szeredi
Cc: Nikolaus Rath
Cc: Liu Yuan
Cc: Has-Wen Nienhuys
---
___
From: Arnd Bergmann [a...@arndb.de]
Sent: 20 July 2012 00:28
To: Tony Prisk
Cc: vt8500-wm8505-linux-ker...@googlegroups.com; Alexey Charkov;
devicetree-disc...@lists.ozlabs.org; Russell King;
linux-kernel@vger.kernel.org;
Make the maximum pipe size referable from a kernel module.
The /proc/sys/fs/pipe-max-size defines an upper limit for the
capacity of a pipe. It is also used as an upper limit of a
fuse read/write request size in this patch series. So, it
is necessary to make it referable from a kernel module.
Hi,
This patch series make maximum read/write request size tunable in FUSE.
Currently, it is limited to FUSE_MAX_PAGES_PER_REQ which is equal
to 32 pages. It is required to change it in order to improve the
throughput since optimized value depends on various factors such
as type and version of
On 2012-07-19 03:05, H Hartley Sweeten wrote:
Use the hw_dev pointer in the comedi_device struct to hold the
pci_dev instead of carrying it in the private data.
My reply to patch 86 has a knock-on effect for this patch...
/* Get the physical address from PCI config */
-
On Wed, 18 Jul 2012, Mel Gorman wrote:
> (Sending as RFC as this one is tricky and as it is timing dependent the
> patch may accidentally be papering over a more fundamental problem. Even
> if it is not, it may be more heavy handed than necessary but am suffering
> from tunnel vision from looking
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)
> +{
> + struct mmc_command *cmd = mrq->cmd;
> + struct mmc_data *data = mrq->data;
> + u8 _cmd[5], *buf;
> +
> + _cmd[0] = 0x40 |
On 07/18/2012 09:19 PM, John Stultz wrote:
> For performance reasons, we maintain ktime_t based duplicates of
> wall_to_monotonic (offs_real) and total_sleep_time (offs_boot).
>
> Since large problems could occur (such as the resume regression
> on 3.5-rc7, or the leapsecond hrtimer issue) if
Hi Mark,
On Wed, Jul 18, 2012 at 15:30:13, Mark Brown wrote:
> On Wed, Jul 18, 2012 at 09:55:57AM +, AnilKumar, Chimata wrote:
>
> > Regulators platform data is added to platform device in MFD driver, which we
> > need for regulator driver, of_regulator_match() is used to check the
> >
On 2012-07-19 03:04, H Hartley Sweeten wrote:
The 'got_regions' variable in the private data is used as a flag
for the detach to know if the pci device has been enabled.
Typically the dev->iobase variable is used to indicate this in
all the other comedi drivers. Do the same here for
On Wed, Jul 18, 2012 at 06:29:44PM -0700, Andrew Morton wrote:
> On Wed, 18 Jul 2012 22:00:48 -0300 Rafael Aquini wrote:
>
> > > So the function needs a better name - one which communicates that it is
> > > a balloon page *for the purposes of processing by the compaction code*.
> > > Making the
a) if alloc_hdlcdev fails, we are going into the free_regions,
and returning out the err (which is 0 by the prev call),
return -ENOMEM if this function fail.
b) setup_device also can fail, as it calls around the register_hdlc_dev
which
is again a macro of the register_netdev.
On Thursday 19 July 2012, Tony Prisk wrote:
> I have no issue with that.
>
> I am mainly concerned with the Wondermedia products at the moment.
>
> Adding device tree support for WM8505 (and WM8650) is my main goal as the
> WM8650
> currently isn't supported and trying to get another board file
On Thu, Jul 19, 2012 at 06:11:15AM -0600, Alex Williamson wrote:
> On Thu, 2012-07-19 at 12:07 +0300, Michael S. Tsirkin wrote:
> > On Wed, Jul 18, 2012 at 05:20:40PM -0600, Alex Williamson wrote:
> > > On Thu, 2012-07-19 at 01:49 +0300, Michael S. Tsirkin wrote:
> > > > On Wed, Jul 18, 2012 at
On Thu, Jun 28, 2012 at 09:02:22AM +0800, Alex Shi wrote:
> Not every tlb_flush execution moment is really need to evacuate all
> TLB entries, like in munmap, just few 'invlpg' is better for whole
> process performance, since it leaves most of TLB entries for later
> accessing.
>
> This patch
2012/7/17 vinayak holikatti :
> On Mon, Jul 16, 2012 at 7:19 PM, Namjae Jeon wrote:
>> Hi Vinayak.
>>> + * ufshcd_pltfrm_remove - remove platform driver routine
>>> + * @pdev: pointer to platform device handle
>>> + *
>>> + * Returns 0 on success, non-zero value on failure
>>> + */
>>> +static
2012/7/19 Tony Prisk :
> From: Arnd Bergmann [a...@arndb.de]
> Sent: 19 July 2012 23:16
> To: vt8500-wm8505-linux-ker...@googlegroups.com
> Cc: Tony Prisk; Alexey Charkov; devicetree-disc...@lists.ozlabs.org; Russell
> King; linux-kernel@vger.kernel.org; linux-arm-ker...@lists.infradead.org
>
Hi Paul,
While running a CPU hotplug stress test on v3.5-rc7+
(mainline commit 8a7298b7805ab) I hit this warning.
I haven't tried to debug this yet...
Line number 1550 maps to:
WARN_ON_ONCE(cpu_is_offline(smp_processor_id()));
inside rcu_do_batch().
Regards,
Srivatsa S. Bhat
[ 1206.095436]
On Thu, 2012-07-19 at 12:07 +0300, Michael S. Tsirkin wrote:
> On Wed, Jul 18, 2012 at 05:20:40PM -0600, Alex Williamson wrote:
> > On Thu, 2012-07-19 at 01:49 +0300, Michael S. Tsirkin wrote:
> > > On Wed, Jul 18, 2012 at 04:26:41PM -0600, Alex Williamson wrote:
> > > > On Thu, 2012-07-19 at
On Thu, Jul 19, 2012 at 06:06:31AM -0600, Alex Williamson wrote:
> On Thu, 2012-07-19 at 12:15 +0300, Michael S. Tsirkin wrote:
> > On Wed, Jul 18, 2012 at 05:22:42PM -0600, Alex Williamson wrote:
> > > I hate reviewing code
> > > > > where I have to differentiate 'l' vs '1'.
> > > >
> > > > l is
On 2012-07-19 02:58, H Hartley Sweeten wrote:
The 'phys_addr' variable in the private data is simply used as
a flag for the detach function to know that the pci device has
been enabled. Use the 'dev->iobase' variable instead as is more
typical for other comedi pci drivers.
I think dev->iobase
On Thu, 2012-07-19 at 12:15 +0300, Michael S. Tsirkin wrote:
> On Wed, Jul 18, 2012 at 05:22:42PM -0600, Alex Williamson wrote:
> > I hate reviewing code
> > > > where I have to differentiate 'l' vs '1'.
> > >
> > > l is an illegal variable name? Switch to a different font.
> >
> > WTF
>
>
From: Arnd Bergmann [a...@arndb.de]
Sent: 19 July 2012 23:16
To: vt8500-wm8505-linux-ker...@googlegroups.com
Cc: Tony Prisk; Alexey Charkov; devicetree-disc...@lists.ozlabs.org; Russell
King; linux-kernel@vger.kernel.org; linux-arm-ker...@lists.infradead.org
Subject: Re: [PATCH 1/1] Add
On 2012-07-19 02:57, H Hartley Sweeten wrote:
The "find pci device" code for this driver was split between
two functions which could cause the driver to walk the pci
bus multiple times while looking for a match.
Actually the original version only walks through the PCI devices once
(due to the
Add missing spin_lock initialization in
amd_iommu_bind_pasid() function and make lockdep happy
again.
Cc: sta...@vger.kernel.org # >= v3.3
Signed-off-by: Joerg Roedel
---
drivers/iommu/amd_iommu_v2.c |2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/iommu/amd_iommu_v2.c
This did not work because devices are not put into the
pt_domain. Fix this.
Cc: sta...@vger.kernel.org
Signed-off-by: Joerg Roedel
---
drivers/iommu/amd_iommu.c | 17 +
1 file changed, 13 insertions(+), 4 deletions(-)
diff --git a/drivers/iommu/amd_iommu.c
On Thu 19-07-12 16:56:18, Aneesh Kumar K.V wrote:
> Kamezawa Hiroyuki writes:
>
> >
> > We test RES_USAGE before taking hugetlb_lock. What prevents some other
> > thread from increasing RES_USAGE after that test?
> >
> > After walking the list we test RES_USAGE after
Deepthi,
[..]
I could implement a sanitize mechanism of the ladder governor that
takes care the "disable" variables of all deeper states are set to 1,
if a state is disabled, and those of all lighter states are set to 0,
if a state is enabled. Do you wish me to do that?
No, I dont think thats
On Thu, Jul 12, 2012 at 12:44:16PM -0500, Rob Clark wrote:
> From: Rob Clark
>
> For devices which have constraints about maximum number of segments
> in an sglist. For example, a device which could only deal with
> contiguous buffers would set max_segment_count to 1.
>
> The initial
On Mon, Jul 16, 2012 at 9:52 PM, Arnd Bergmann wrote:
> On Monday 16 July 2012, James Bottomley wrote:
>> On Fri, 2012-07-13 at 15:45 +, Arnd Bergmann wrote:
>> > On Friday 13 July 2012, Vinayak Holikatti wrote:
>> > > This patch set adds following features
>> > > - Seprates PCI specific
Anton,
> Hm. So Myungjoo thinks that some of the features are compatible. Which do
> you guys think are not compatible? Is this because charger manager does
> everything using a regulator framework? That is, quoting you:
>
> "The challenge I see in implementing the above requirements in
Kamezawa Hiroyuki writes:
>
> We test RES_USAGE before taking hugetlb_lock. What prevents some other
> thread from increasing RES_USAGE after that test?
>
> After walking the list we test RES_USAGE after dropping hugetlb_lock.
> What prevents another thread from
On Wed, July 18, 2012 11:46 pm, Chris Ball wrote:
> Hi Yaniv,
>
> On Thu, Jun 28 2012, Yaniv Gardi wrote:
>> This feature delete the unmap memory region of the eMMC card,
>> by writing to a specific register in the EXT_CSD
>> unmap region is the memory region that were previously deleted
>> (by
On Thursday 19 July 2012, Tony Prisk wrote:
> Given that there have been no replies to this thread, and the restart patch
> has
> now been accepted using 'wmt' as the vendor namespace - would it be safe to
> assume we should formalize this in the vendor-bindings.txt?
>
> I'd like to try and have
On 07/18/2012 05:27 PM, Frederic Weisbecker wrote:
On Wed, Jul 18, 2012 at 04:00:46PM +0530, Naveen N. Rao wrote:
Please find v2 of the patch from Prasad, based on Peter Zijlstra's
feedback. This applies on top of v3.5-rc7. This has been tested and
found to work fine by Edjunior.
Regards,
On 07/18/2012 08:08 PM, Carsten Emde wrote:
> On 07/18/2012 01:48 PM, Deepthi Dharwar wrote:
>> On 07/18/2012 04:32 PM, Carsten Emde wrote:
>>> On 07/18/2012 08:36 AM, Deepthi Dharwar wrote:
On 07/18/2012 12:29 AM, Carsten Emde wrote:
> There are two cpuidle governors ladder and menu.
We validate irq pin number when routing is setup, so
code handling illegal irq # in pic and ioapic on each injection
is never called.
Drop it.
Signed-off-by: Michael S. Tsirkin
---
Note: this is on top of
[PATCHv2] kvm: fix race with level interrupts
as these patches touch the same
Use PIC_NUM_PINS instead of hard-coded 16 for pic pins.
Signed-off-by: Michael S. Tsirkin
---
arch/x86/kvm/irq.h | 2 +-
virt/kvm/irq_comm.c | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/x86/kvm/irq.h b/arch/x86/kvm/irq.h
index 2086f2b..2d03568 100644
---
The profile sensor clickpad in a Cr-48 Chromebook does a reasonable job of
tracking individual fingers. This tracking isn't perfect, but, experiments
show that it works better than just passing "semi-mt" data to userspace,
and making userspace try to deduce where the fingers are given a bounding
When more than 1 source id is in use for the same GSI, we have the
following race related to handling irq_states race:
CPU 0 clears bit 0. CPU 0 read irq_state as 0. CPU 1 sets level to 1.
CPU 1 calls kvm_ioapic_set_irq(1). CPU 0 calls kvm_ioapic_set_irq(0).
Now ioapic thinks the level is 0 but
Hi Duan,
On Wed, Jul 18, 2012 at 10:38:16PM +0800, Duan Jiong wrote:
>
> Signed-off-by: Duan Jiong
> ---
> drivers/media/video/smiapp/smiapp-core.c |1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/drivers/media/video/smiapp/smiapp-core.c
> b/drivers/media/video/smiapp/smiapp-core.c
On 2012-07-19 11:30, Ian Abbott wrote:
On 2012-07-19 02:39, H Hartley Sweeten wrote:
Use the hw_dev pointer in the comedi_device struct to hold the
pci_dev instead of carrying it in the private data.
Since the pci_dev is no longer held in the provate data, we can
also cleanup the detach a bit.
On 2012-07-19 11:27, Ian Abbott wrote:
On 2012-07-19 11:10, Ian Abbott wrote:
On 2012-07-19 02:37, H Hartley Sweeten wrote:
Use the hw_dev pointer in the comedi_device struct to hold the
pci_dev instead of carrying it in the private data.
Since the pci_dev is no longer held in the provate
On Mo, 16.07.2012, 17:24, Christoph Paasch wrote:
> You should do jiffies_to_msecs(tp->srtt) >> 3.
>
> The RTT is already exposed by tcp_info anyway... (see tcp_get_info() - where
> you also see the bitshift)
thanks a lot. rtt is output for completion's sake, it helps in diagnosis.
here my
On 2012-07-19 02:39, H Hartley Sweeten wrote:
Use the hw_dev pointer in the comedi_device struct to hold the
pci_dev instead of carrying it in the private data.
Since the pci_dev is no longer held in the provate data, we can
also cleanup the detach a bit. Remove the IS_ENABLED() tests in
the
On Thu, Jul 19, 2012 at 09:00:51AM +0800, Li Zefan wrote:
> > static struct cgroup_subsys_state *cgrp_create(struct cgroup *cgrp)
>
> > {
> > struct cgroup_netprio_state *cs;
> > - int ret;
> > + int ret = -EINVAL;
> >
> > cs =
On Thu, Jul 19, 2012 at 07:23:07PM +0900, Kamezawa Hiroyuki wrote:
>(2012/07/19 18:29), Michal Hocko wrote:
>>On Wed 18-07-12 19:08:54, Wanpeng Li wrote:
>>>use exist interface mem_cgroup_css instead of >css.
>>
>>This interface has been added to enable mem->css outside of
>>mm/memcontrol.c (where
(2012/07/19 18:41), Aneesh Kumar K.V wrote:
Li Zefan writes:
on 2012/7/19 10:55, Aneesh Kumar K.V wrote:
Andrew Morton writes:
On Wed, 18 Jul 2012 11:04:09 +0530
"Aneesh Kumar K.V" wrote:
From: "Aneesh Kumar K.V"
Since we cannot fail in hugetlb_cgroup_move_parent, we don't really
July 17, 2012, Thomas Abraham wrote:
> Some platforms allow for clock gating and control of bus interface unit clock
> and card interface unit clock. Add support for clock lookup of optional biu
> and ciu clocks for clock gating and clock speed determination.
>
> Signed-off-by: Abhilash Kesavan
On 2012-07-19 11:10, Ian Abbott wrote:
On 2012-07-19 02:37, H Hartley Sweeten wrote:
Use the hw_dev pointer in the comedi_device struct to hold the
pci_dev instead of carrying it in the private data.
Since the pci_dev is no longer held in the provate data, we can
also cleanup the detach a bit.
(2012/07/19 18:29), Michal Hocko wrote:
On Wed 18-07-12 19:08:54, Wanpeng Li wrote:
use exist interface mem_cgroup_css instead of >css.
This interface has been added to enable mem->css outside of
mm/memcontrol.c (where we define struct mem_cgroup). There is one user
left
> Caused by commit adc8d746caa6 ("tty: move the termios object into the
> tty"). Grep and build testing are your friends ...
>
> I have used the tty tree from next-20120712 again for today.
Doh, patch sent
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body
On Thu, Jul 19, 2012 at 05:38:35PM +0800, Gavin Shan wrote:
>On Thu, Jul 19, 2012 at 05:23:09PM +0800, Wanpeng Li wrote:
>>On Thu, Jul 19, 2012 at 12:14:20PM +0300, Kirill A. Shutemov wrote:
>>>On Wed, Jul 18, 2012 at 11:05:30AM +0800, Wanpeng Li wrote:
wrap mem_cgroup_from_css function to
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 changed, 11 insertions(+), 1 deletions(-)
>
> diff
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 (pfn_valid(pfn)) {
> @@ -949,13 +952,15 @@
301 - 400 of 952 matches
Mail list logo
