On Mon, Nov 04, 2013 at 02:58:28PM +, Mel Gorman wrote:
On Wed, Oct 16, 2013 at 10:54:29AM -0500, Alex Thorlton wrote:
Hi guys,
I ran into a bug a week or so ago, that I believe has something to do
with NUMA balancing, but I'm having a tough time tracking down exactly
what is
On Sun, Nov 3, 2013 at 4:10 PM, Linus Torvalds
torva...@linux-foundation.org wrote:
The reason I mention it is because I've been mulling over something
Dirk Hohndel said during LinuxCon EU and the kernel summit. He asked
at the QA session whether we could do a release with just stability
and
Hey Jens, sorry for being late with this - anyways, it's roughly the same set of
patches you had queued up before plus a few minor fixes, but it's been rebased
onto your for-3.13/core branch.
The following changes since commit febca1baea1cfe2d7a0271385d89b03d5fb34f94:
block: setup bi_vcnt on
* H. Peter Anvin h...@zytor.com wrote:
8192 maybe?
Yeah, that makes more sense I guess.
Thanks,
Ingo
--
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
On Mon, Nov 04, 2013 at 10:06:00AM -0500, Mikulas Patocka wrote:
On Fri, 1 Nov 2013, Jens Axboe wrote:
On 11/01/2013 07:59 AM, Mike Snitzer wrote:
Add the missing bi_remaining increment, required by the block layer's
new bio-chaining code, to both the verity and old snapshot DM
From: Govindarajulu Varadarajan govindarajul...@gmail.com
Date: Sat, 2 Nov 2013 19:17:43 +0530
@@ -1030,10 +1030,8 @@ static void ni65_xmit_intr(struct net_device *dev,int
csr0)
}
#ifdef XMT_VIA_SKB
- if(p-tmd_skb[p-tmdlast]) {
-
On 11/04/2013 01:07 PM, Kent Overstreet wrote:
Hey Jens, sorry for being late with this - anyways, it's roughly the same set
of
patches you had queued up before plus a few minor fixes, but it's been rebased
onto your for-3.13/core branch.
Merge window is a little later this time, and since
On Mon, Nov 04, 2013 at 09:08:12AM -0700, Greg Edwards wrote:
When determining the page size we could use to map with the IOMMU, the
page size should also be aligned with the hva, not just the gfn. The
gfn may not reflect the real alignment within the hugetlbfs file.
Signed-off-by: Greg
On Mon, Nov 04, 2013 at 01:12:17PM -0700, Jens Axboe wrote:
On 11/04/2013 01:07 PM, Kent Overstreet wrote:
Hey Jens, sorry for being late with this - anyways, it's roughly the same
set of
patches you had queued up before plus a few minor fixes, but it's been
rebased
onto your
* Arnaldo Carvalho de Melo a...@infradead.org wrote:
From: Arnaldo Carvalho de Melo a...@ghostprotocols.net
Hi Ingo,
Please consider pulling,
- Arnaldo
The following changes since commit 46d525eae2a076adfde92dca1db12d9a3b8ad8bb:
perf test: Update command line callchain
On 11/04/2013 01:16 PM, Kent Overstreet wrote:
On Mon, Nov 04, 2013 at 01:12:17PM -0700, Jens Axboe wrote:
On 11/04/2013 01:07 PM, Kent Overstreet wrote:
Hey Jens, sorry for being late with this - anyways, it's roughly the same
set of
patches you had queued up before plus a few minor fixes,
Am 04.11.2013 20:49, schrieb Geert Uytterhoeven:
On Mon, Nov 4, 2013 at 6:00 PM, Alexander Holler hol...@ahsoftware.de wrote:
3.14
3.141
3.1415
3.14159
3.141592
3.1415926
(...)
4.0
Since when does \pi converge to 4.0?
The attention span of most people is usually limited, so they won't
Commit-ID: 9ef0438a957937bf0edc26d58bce891034ff9e30
Gitweb: http://git.kernel.org/tip/9ef0438a957937bf0edc26d58bce891034ff9e30
Author: Arnaldo Carvalho de Melo a...@redhat.com
AuthorDate: Thu, 24 Oct 2013 17:36:31 -0300
Committer: Arnaldo Carvalho de Melo a...@redhat.com
CommitDate: Mon,
Commit-ID: fedd63d3cdc9004df43b02df5c874b8957992fe8
Gitweb: http://git.kernel.org/tip/fedd63d3cdc9004df43b02df5c874b8957992fe8
Author: Frederic Weisbecker fweis...@gmail.com
AuthorDate: Wed, 11 Sep 2013 17:18:09 +0200
Committer: Arnaldo Carvalho de Melo a...@redhat.com
CommitDate: Mon, 4
Commit-ID: f852fd621ca19f557f2e3d05900366be7c7afb83
Gitweb: http://git.kernel.org/tip/f852fd621ca19f557f2e3d05900366be7c7afb83
Author: Adrian Hunter adrian.hun...@intel.com
AuthorDate: Fri, 1 Nov 2013 15:51:29 +0200
Committer: Arnaldo Carvalho de Melo a...@redhat.com
CommitDate: Mon, 4
Commit-ID: 28e962b9d79f496f214d7fc8ffd1a3f2a67e9090
Gitweb: http://git.kernel.org/tip/28e962b9d79f496f214d7fc8ffd1a3f2a67e9090
Author: Adrian Hunter adrian.hun...@intel.com
AuthorDate: Fri, 1 Nov 2013 15:51:31 +0200
Committer: Arnaldo Carvalho de Melo a...@redhat.com
CommitDate: Mon, 4
Commit-ID: 7ea95727af571d592c9d6aa7627690d44b114a2d
Gitweb: http://git.kernel.org/tip/7ea95727af571d592c9d6aa7627690d44b114a2d
Author: Adrian Hunter adrian.hun...@intel.com
AuthorDate: Fri, 1 Nov 2013 15:51:30 +0200
Committer: Arnaldo Carvalho de Melo a...@redhat.com
CommitDate: Mon, 4
Commit-ID: 4dfced359fbc719a35527416f1b4b3999647f68b
Gitweb: http://git.kernel.org/tip/4dfced359fbc719a35527416f1b4b3999647f68b
Author: Namhyung Kim namhyung@lge.com
AuthorDate: Fri, 13 Sep 2013 16:28:57 +0900
Committer: Arnaldo Carvalho de Melo a...@redhat.com
CommitDate: Mon, 4 Nov
Commit-ID: 8a0c4c2843d3b72e23c3c12079b8d5c3ae99f3e3
Gitweb: http://git.kernel.org/tip/8a0c4c2843d3b72e23c3c12079b8d5c3ae99f3e3
Author: Adrian Hunter adrian.hun...@intel.com
AuthorDate: Fri, 1 Nov 2013 15:51:32 +0200
Committer: Arnaldo Carvalho de Melo a...@redhat.com
CommitDate: Mon, 4
Commit-ID: 91aba0a62e24ff7a567e13e1d88deab711df6f0f
Gitweb: http://git.kernel.org/tip/91aba0a62e24ff7a567e13e1d88deab711df6f0f
Author: Namhyung Kim namhyung@lge.com
AuthorDate: Fri, 1 Nov 2013 16:33:13 +0900
Committer: Arnaldo Carvalho de Melo a...@redhat.com
CommitDate: Mon, 4 Nov
Commit-ID: 1b372ca52a02cc97520c13d79bdfb0a7ff81b772
Gitweb: http://git.kernel.org/tip/1b372ca52a02cc97520c13d79bdfb0a7ff81b772
Author: Yoshihiro YUNOMAE yoshihiro.yunomae...@hitachi.com
AuthorDate: Fri, 1 Nov 2013 17:53:53 -0400
Committer: Arnaldo Carvalho de Melo a...@redhat.com
Commit-ID: 87b955247d71975460774435241be3aa05218a7b
Gitweb: http://git.kernel.org/tip/87b955247d71975460774435241be3aa05218a7b
Author: Adrian Hunter adrian.hun...@intel.com
AuthorDate: Fri, 1 Nov 2013 15:51:36 +0200
Committer: Arnaldo Carvalho de Melo a...@redhat.com
CommitDate: Mon, 4
Commit-ID: d37a92dcb45094dc02836c8a77c693c6f9916fb2
Gitweb: http://git.kernel.org/tip/d37a92dcb45094dc02836c8a77c693c6f9916fb2
Author: Namhyung Kim namhyung@lge.com
AuthorDate: Fri, 1 Nov 2013 16:33:14 +0900
Committer: Arnaldo Carvalho de Melo a...@redhat.com
CommitDate: Mon, 4 Nov
Commit-ID: 026359658aecd348bc5c4a136a26f204b169103b
Gitweb: http://git.kernel.org/tip/026359658aecd348bc5c4a136a26f204b169103b
Author: Adrian Hunter adrian.hun...@intel.com
AuthorDate: Fri, 1 Nov 2013 15:51:33 +0200
Committer: Arnaldo Carvalho de Melo a...@redhat.com
CommitDate: Mon, 4
Commit-ID: cc03c54296ccbeca5363dfe8f49af42d14960f28
Gitweb: http://git.kernel.org/tip/cc03c54296ccbeca5363dfe8f49af42d14960f28
Author: Namhyung Kim namhyung@lge.com
AuthorDate: Fri, 1 Nov 2013 16:33:15 +0900
Committer: Arnaldo Carvalho de Melo a...@redhat.com
CommitDate: Mon, 4 Nov
Commit-ID: 091a4ef5a94d46d26a05f0c32d2f64800ed91306
Gitweb: http://git.kernel.org/tip/091a4ef5a94d46d26a05f0c32d2f64800ed91306
Author: Adrian Hunter adrian.hun...@intel.com
AuthorDate: Fri, 1 Nov 2013 15:51:37 +0200
Committer: Arnaldo Carvalho de Melo a...@redhat.com
CommitDate: Mon, 4
Commit-ID: 1e7ed5ec54e3998bda6ea625599a0644404cb421
Gitweb: http://git.kernel.org/tip/1e7ed5ec54e3998bda6ea625599a0644404cb421
Author: Adrian Hunter adrian.hun...@intel.com
AuthorDate: Fri, 1 Nov 2013 15:51:35 +0200
Committer: Arnaldo Carvalho de Melo a...@redhat.com
CommitDate: Mon, 4
Commit-ID: 6e6dc401d528e3b64626de82322fa237f1c1e576
Gitweb: http://git.kernel.org/tip/6e6dc401d528e3b64626de82322fa237f1c1e576
Author: Jiri Olsa jo...@redhat.com
AuthorDate: Sat, 26 Oct 2013 20:53:14 +0200
Committer: Arnaldo Carvalho de Melo a...@redhat.com
CommitDate: Mon, 4 Nov 2013
Commit-ID: 42d88910c717ba21089251d0ca559abfef0df22d
Gitweb: http://git.kernel.org/tip/42d88910c717ba21089251d0ca559abfef0df22d
Author: Adrian Hunter adrian.hun...@intel.com
AuthorDate: Fri, 1 Nov 2013 15:51:38 +0200
Committer: Arnaldo Carvalho de Melo a...@redhat.com
CommitDate: Mon, 4
Commit-ID: c6c2b960b7a4105f096499fba3df65d6c0272a20
Gitweb: http://git.kernel.org/tip/c6c2b960b7a4105f096499fba3df65d6c0272a20
Author: Steven Rostedt srost...@redhat.com
AuthorDate: Fri, 1 Nov 2013 17:53:59 -0400
Committer: Arnaldo Carvalho de Melo a...@redhat.com
CommitDate: Mon, 4 Nov
Commit-ID: 0970b5f438261216afcd0ccaa2fcfffc83df7ca2
Gitweb: http://git.kernel.org/tip/0970b5f438261216afcd0ccaa2fcfffc83df7ca2
Author: Steven Rostedt (Red Hat) rost...@goodmis.org
AuthorDate: Fri, 1 Nov 2013 17:53:55 -0400
Committer: Arnaldo Carvalho de Melo a...@redhat.com
CommitDate:
Commit-ID: 5efb9fbd5f1bfe4435bd0a3ea5f0e187875509c2
Gitweb: http://git.kernel.org/tip/5efb9fbd5f1bfe4435bd0a3ea5f0e187875509c2
Author: Steven Rostedt (Red Hat) rost...@goodmis.org
AuthorDate: Fri, 1 Nov 2013 17:53:58 -0400
Committer: Arnaldo Carvalho de Melo a...@redhat.com
CommitDate:
Hi
Thanks for your reply
On Mon, Nov 4, 2013 at 10:53 AM, Andi Kleen a...@firstfloor.org wrote:
Anatol Pomozov anatol.pomo...@gmail.com writes:
One idea is not to use the spin_lock. It is the 'fair spin_lock' that
has scalability problems
http://pdos.csail.mit.edu/papers/linux:lock.pdf
Commit-ID: 18900af8292180151c82f0762506fa0740aa54a5
Gitweb: http://git.kernel.org/tip/18900af8292180151c82f0762506fa0740aa54a5
Author: Steven Rostedt (Red Hat) rost...@goodmis.org
AuthorDate: Fri, 1 Nov 2013 17:53:54 -0400
Committer: Arnaldo Carvalho de Melo a...@redhat.com
CommitDate:
Commit-ID: 0883d9d730fc294c3d90ebd190b94e5782ead316
Gitweb: http://git.kernel.org/tip/0883d9d730fc294c3d90ebd190b94e5782ead316
Author: Steven Rostedt (Red Hat) rost...@goodmis.org
AuthorDate: Fri, 1 Nov 2013 17:53:57 -0400
Committer: Arnaldo Carvalho de Melo a...@redhat.com
CommitDate:
Commit-ID: 6d862b8c14ba539c7c87ffc77f2e1d6dc9630c4d
Gitweb: http://git.kernel.org/tip/6d862b8c14ba539c7c87ffc77f2e1d6dc9630c4d
Author: Steven Rostedt srost...@redhat.com
AuthorDate: Fri, 1 Nov 2013 17:54:00 -0400
Committer: Arnaldo Carvalho de Melo a...@redhat.com
CommitDate: Mon, 4 Nov
Commit-ID: b30f75eba27a9ab0704cbc501e9be3b025ce56fe
Gitweb: http://git.kernel.org/tip/b30f75eba27a9ab0704cbc501e9be3b025ce56fe
Author: Howard Cochran hcoch...@lexmark.com
AuthorDate: Fri, 1 Nov 2013 17:53:56 -0400
Committer: Arnaldo Carvalho de Melo a...@redhat.com
CommitDate: Mon, 4 Nov
Commit-ID: 4bceffbc26fab2444742db59c6f8124c29e41369
Gitweb: http://git.kernel.org/tip/4bceffbc26fab2444742db59c6f8124c29e41369
Author: Namhyung Kim namhyung@lge.com
AuthorDate: Fri, 1 Nov 2013 16:33:12 +0900
Committer: Arnaldo Carvalho de Melo a...@redhat.com
CommitDate: Mon, 4 Nov
Commit-ID: ac6976255076d4bf761abfbecb19d46af5b88046
Gitweb: http://git.kernel.org/tip/ac6976255076d4bf761abfbecb19d46af5b88046
Author: Namhyung Kim namhyung@lge.com
AuthorDate: Fri, 1 Nov 2013 16:33:11 +0900
Committer: Arnaldo Carvalho de Melo a...@redhat.com
CommitDate: Mon, 4 Nov
Commit-ID: 162f0befda3becc2cc9f44075fccc030e55baec1
Gitweb: http://git.kernel.org/tip/162f0befda3becc2cc9f44075fccc030e55baec1
Author: Frederic Weisbecker fweis...@gmail.com
AuthorDate: Wed, 11 Sep 2013 16:18:24 +0200
Committer: Arnaldo Carvalho de Melo a...@redhat.com
CommitDate: Mon, 4
On 11/04/2013 01:10 AM, Linus Torvalds wrote:
...
Anyway..
Onto a totally different topic: we're getting to release numbers where
I have to take off my socks to count that high again. I'm ok with
3.low teens, but I don't want us to get to the kinds of crazy
numbers we had in the 2.x series,
Commit-ID: 1902efe7f626fdebe1520f5ff11f1309ec506708
Gitweb: http://git.kernel.org/tip/1902efe7f626fdebe1520f5ff11f1309ec506708
Author: Frederic Weisbecker fweis...@gmail.com
AuthorDate: Wed, 11 Sep 2013 16:56:44 +0200
Committer: Arnaldo Carvalho de Melo a...@redhat.com
CommitDate: Mon, 4
Commit-ID: b9c5143a012a543c4ee872498d6dbae5c10beb2e
Gitweb: http://git.kernel.org/tip/b9c5143a012a543c4ee872498d6dbae5c10beb2e
Author: Frederic Weisbecker fweis...@gmail.com
AuthorDate: Wed, 11 Sep 2013 14:46:56 +0200
Committer: Arnaldo Carvalho de Melo a...@redhat.com
CommitDate: Mon, 4
This solution pretty-much equivalent to per-CPU data structures. And
No it's not, it doesn't require one queue per CPU.
A CPU these days isn't really a CPU anymore, but often a CPU thread,
which is much more light weight. So having a queue per CPU is often
total overkill, and amplifies any per
Dave,
Please accept the following pull request intended for the 3.13 tree...
I had intended to pass most of these to you as much as two weeks ago.
Unfortunately, I failed to account for the effects of bad Internet
connections and my own fatique/laziness while traveling. On the bright
side, at
I noticed that srcu_read_lock/unlock both have a memory barrier,
so just by moving srcu_read_unlock earlier we can get rid of
one call to smp_mb() using smp_mb__after_srcu_read_unlock instead.
Unsurprisingly, the gain is small but measureable using the unit test
microbenchmark:
before
srcu read lock/unlock include a full memory barrier
but that's an implementation detail.
Add an API for make memory fencing explicit for
users that need this barrier, to make sure we
can change it as needed without breaking all users.
Acked-by: Paul E. McKenney paul...@linux.vnet.ibm.com
On Wed, 30 Oct 2013, Daniel Kiper wrote:
Hi,
Here is a short summary of our discussion. It looks
that we have two choices right now:
- chainloader,
- multiboot2 protocol.
chainloader solution could be implemented quite easily. Some code should be
added for command line parsing.
Sure; this is your baby :) Why don't you handle it via your tree,
since it's more related to xen than any PCI core stuff.
Acked-by: Bjorn Helgaas bhelg...@google.com
Definitly fixed in v3.12. Just tested it and it works.
George, Ian, how do I close a bug in
From: hayeswang hayesw...@realtek.com
Date: Thu, 31 Oct 2013 13:52:38 +0800
From: David Miller [mailto:da...@davemloft.net]
Sent: Thursday, October 31, 2013 5:05 AM
From: Hayes Wang hayesw...@realtek.com
Date: Wed, 30 Oct 2013 15:13:39 +0800
[...]
Basically, your driver will now queue up
On Mon, Nov 04, 2013 at 08:11:27PM +0100, Peter Zijlstra wrote:
On Mon, Nov 04, 2013 at 08:27:32AM -0800, Paul E. McKenney wrote:
All this is leading me to suggest the following shortenings of names:
smp_load_with_acquire_semantics() - smp_load_acquire()
On Mon, Nov 04, 2013 at 06:21:05PM +0800, Gu Zheng wrote:
Introduce flag KM_ZERO which is used to alloc zeroed entry, and convert
kmem_{zone_}zalloc to call kmem_{zone_}alloc() with KM_ZERO directly,
in order to avoid the setting to zero step.
And following Dave's suggestion, make
On Mon, Nov 04, 2013 at 10:36:17PM +0200, Michael S. Tsirkin wrote:
srcu read lock/unlock include a full memory barrier
but that's an implementation detail.
Add an API for make memory fencing explicit for
users that need this barrier, to make sure we
can change it as needed without breaking
On Mon, 4 Nov 2013 12:41:52 +0200 (EET) Kirill A. Shutemov
kirill.shute...@linux.intel.com wrote:
Kirill A. Shutemov wrote:
Matthew noticed that hugetlb doesn't participate in ASLR on x86-64.
The reason is genereic hugetlb_get_unmapped_area() which is used on
x86-64. It doesn't support
On Mon, Nov 04, 2013 at 09:24:58AM -0800, James Ralston wrote:
This patch adds the AHCI-mode SATA Device IDs for the Intel Wildcat Point-LP
PCH.
Signed-off-by: James Ralston james.d.rals...@intel.com
Applied to for-3.13 w/ stable cc'd.
Thanks.
--
tejun
--
To unsubscribe from this list:
On Mon, Nov 04, 2013 at 08:18:11PM +0100, Peter Zijlstra wrote:
On Mon, Nov 04, 2013 at 08:11:27PM +0100, Peter Zijlstra wrote:
+#define smp_load_acquire(p, v)
\
I R idiot!! :-)
OK, I did miss this one as well... :-/
On 11/04/13 14:49, Oleg Nesterov wrote:
On 10/29, Oleg Nesterov wrote:
David. Perhaps we can avoid the new hook altogether? What if we do
the simple change below (it ignores powerpc) ?
Then arm can add unsigned long ixol[2] into its arch_uprobe, and
arch_uprobe_analyze_insn() can initialize
Add support for battery charge thresholds in new Sandy Bridge and Ivy Bridge
ThinkPads. Based on the unofficial documentation in tpacpi-bat.
The threshold files support the values '0' for the controller's default,
and 1-99 as percentages. Values outside of that range are rejected. The
behaviour
On Monday 2013-11-04 01:10, Linus Torvalds wrote:
Onto a totally different topic: we're getting to release numbers where
I have to take off my socks to count that high again. I'm ok with
3.low teens [...] [4.0 ok, after 3.19 (or whatever),]
What would you do when the major number becomes such
Quoting Tejun Heo (t...@kernel.org):
Hello, Serge.
On Tue, Jul 23, 2013 at 3:28 PM, Serge Hallyn serge.hal...@ubuntu.com wrote:
On Tue, Jul 23, 2013 at 02:04:26PM -0500, Serge Hallyn wrote:
If task A is uid 1000 on the host, and creates task B as uid X in a new
user namespace, then
Add this to try this...
Chen Gang's defect is because his git repository branch
had a commit he authored but where did not add his signature.
Also, there's a defect in function vcs_find_signers.
It should only return the commit count and array references.
If there are no signers in the commit
On 05/11/13 04:08, Frank Haverkamp wrote:
Selecting interface names via configuration option is obsolete.
Don't do this. You are adding completely new code, so there is no reason
to post a patch full of code that is known to be incorrect, followed by
a set of patches fixing things. Just post the
On Fri, 01 Nov 2013 18:31:40 +0400 Maxim Patlasov mpatla...@parallels.com
wrote:
strictlimit feature was introduced to enforce per-bdi dirty limits for
FUSE which sets bdi max_ratio to 1% by default:
http://www.http.com//article.gmane.org/gmane.linux.kernel.mm/105809
However the feature
Hello,
On Mon, Nov 04, 2013 at 09:51:35PM +, Serge E. Hallyn wrote:
Do you have a list of such issues which you see with delegation? That is,
cases where, if ownership of a subtree is granted to a non-root user,
that user can affect tasks owned by other users who are in other
cgroups?
A
Due to USB controllers may have different restrictions, usb gadget layer
needs to provide a generic way to inform gadget functions to complain
with non-standard requirements.
This patch adds 'quirk_ep_out_aligned_size' field to struct usb_gadget
to inform when controller's epout requires buffer
This patch moves all bitflags to the end of usb_gadget struct in order
to improve readability.
Signed-off-by: David Cohen david.a.co...@linux.intel.com
---
include/linux/usb/gadget.h | 19 ++-
1 file changed, 10 insertions(+), 9 deletions(-)
diff --git
DWC3 requires epout to have buffer size aligned to MaxPacketSize value.
This patch adds necessary quirk for it.
Signed-off-by: David Cohen david.a.co...@linux.intel.com
---
drivers/usb/dwc3/gadget.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/drivers/usb/dwc3/gadget.c
Check gadget.quirk_ep_out_aligned_size to decide if buffer size requires
to be aligned to maxpacketsize of an out endpoint. ffs_epfile_io() needs
to pad epout buffer to match above condition if quirk is found.
Signed-off-by: David Cohen david.a.co...@linux.intel.com
---
drivers/usb/gadget/f_fs.c
Hi,
These patches are a proposal to add gadget quirks in an immediate objective to
adapt f_fs when using DWC3 controller. But the quirk solution is generic and
can be used by other controllers to adapt gadget functions to their
non-standard restrictions.
This change is necessary to make
On Mon, Nov 04, 2013 at 06:08:01PM +0100, Frank Haverkamp wrote:
+if GENWQE
+
+config GENWQE_DEVNAME
+string Name for sysfs and device nodes
+ default genwqe
+help
+ Select alternate name for sysfs and device nodes.
+
+endif
Why is this still here? I thought
DWC3 requires epout to have buffer size aligned to MaxPacketSize value.
This patch sets necessary quirk for it.
Signed-off-by: David Cohen david.a.co...@linux.intel.com
---
Changes from v4 to v4.1:
- just updated patch's subject. No actual code changed.
drivers/usb/dwc3/gadget.c | 6 ++
1
On Mon, Nov 04, 2013 at 05:41:27PM +0100, Frank Haverkamp wrote:
Hi Greg,
Am Mittwoch, den 30.10.2013, 10:44 -0700 schrieb Greg KH:
On Wed, Oct 30, 2013 at 10:32:58AM +0100, Frank Haverkamp wrote:
+/*
+ * Create device_attribute structures / params: name, mode, show, store
+ *
I'm hardly an expert here, but the appears sane to me. Perhaps a
comment above the PYTHON_VERS describing what valid values are would
be helpful. Otherwise, looks good to me.
On Mon, Nov 4, 2013 at 12:32 AM, Johannes Berg
johan...@sipsolutions.net wrote:
On Fri, 2013-11-01 at 17:19 -0400, Steven
On Thu, 31 Oct 2013 16:12:44 -0700 Joe Perches j...@perches.com wrote:
This now uses the $balanced_parens test and also makes
the test depend on perl v5.10 and higher.
What happens if one uses an older perl version? A mysterious-looking
splat, I assume?
It would be nicer to have some
On Mon, 2013-11-04 at 14:21 -0800, Andrew Morton wrote:
On Thu, 31 Oct 2013 16:12:44 -0700 Joe Perches j...@perches.com wrote:
This now uses the $balanced_parens test and also makes
the test depend on perl v5.10 and higher.
What happens if one uses an older perl version? A
On 11/04/2013 06:00 AM, Geert Uytterhoeven wrote:
do_div() (called by sector_div() if CONFIG_LBDAF=y) is meant for divisions
of 64-bit number by 32-bit numbers. Passing 64-bit divisor types caused
issues in the past on 32-bit platforms, cfr. commit
ea077b1b96e073eac5c3c5590529e964767fc5f7
On Sun, Nov 03, 2013 at 03:39:14PM -0800, Linus Torvalds wrote:
On Sun, Nov 3, 2013 at 11:54 AM, Al Viro v...@zeniv.linux.org.uk wrote:
IIRC, at some point such an attempt has seriously hurt iget() on 32bit
boxen, so we ended up deciding not to go there. Had been years ago,
though...
Hi,
When I'm trying XIP on ext2, I find that xip does not work on ext2
with latest kernel.
Reproduce steps:
Compile kernel with following configs:
CONFIG_BLK_DEV_XIP=y
CONFIG_EXT2_FS_XIP=y
And run following commands:
# mke2fs -b 4096 /dev/ram0
# mount -t ext2 -o xip /dev/ram0 /mnt/ramdisk/
# dd
Ingo,
Sorry for the late response. My old 4 socket Westmere
test machine went down and I have to find a new one,
which is a 4 socket Ivybridge machine with 15 cores per socket.
I've updated the workload as a perf benchmark (see patch)
attached. The workload will mmap, then access memory
in
On 11/04/2013 12:11 PM, Ingo Molnar wrote:
* H. Peter Anvin h...@zytor.com wrote:
8192 maybe?
Yeah, that makes more sense I guess.
However, I still have serious issues with crap like this because
randconfig is basically broken. If nothing else we need to get that
feedback to the
On 11/04/2013 07:10 AM, Fengguang Wu wrote:
Hi Jens,
I'm not very sure about this bisect, but anyway it'd be good to inform
you of a possible problem on commit
commit 3a02db083a78c9f3c9b69305ab513f9422d91b08
Author: Jens Axboe ax...@kernel.dk
Date: Fri May 24 20:22:33 2013 +0200
The reason I mention it is because I've been mulling over something
Dirk Hohndel said during LinuxCon EU and the kernel summit. He asked
at the QA session whether we could do a release with just stability
and bug-fixes, and I pooh-poohed it because I didn't see most of us
having the attention
Hi,
Le 04/11/2013 23:20, Darren Hart a écrit :
I'm hardly an expert here, but the appears sane to me. Perhaps a
comment above the PYTHON_VERS describing what valid values are would
be helpful. Otherwise, looks good to me.
Expected values are python and python3 for PYTHON_VERS.
trace-cmd has
Am 04.11.2013 20:49, schrieb Geert Uytterhoeven:
On Mon, Nov 4, 2013 at 6:00 PM, Alexander Holler hol...@ahsoftware.de wrote:
3.14
3.141
3.1415
3.14159
3.141592
3.1415926
(...)
4.0
Since when does \pi converge to 4.0?
Since 3.12 3.9. ;)
--
To unsubscribe from this list: send the line
On Mon, 2013-11-04 at 11:29 -0700, Jim Davis wrote:
Building with the attached random configuration file,
security/integrity/digsig.c:70:5: error: redefinition of
‘integrity_init_keyring
’
int integrity_init_keyring(const unsigned int id)
^
In file included from
Am Montag, 4. November 2013, 13:24:10 schrieb Linus Walleij:
In my driver, I have the one entry per pin support for all my
properties instead of just the function property, like the drive_str
property below:
+ grp_1 {
+ brcm,pins = pin1, pin2,
Now that immutable biovecs is in, these are the remaining patches required for
my DIO rewrite, along with some related cleanup/refactoring.
The key enabler is patch 4 - making generic_make_request() handle arbitary sized
bios. This takes what was once bio_add_page()'s responsibility and pushes it
It was being open coded in a few places.
Signed-off-by: Kent Overstreet k...@daterainc.com
Cc: Jens Axboe ax...@kernel.dk
Cc: Joern Engel jo...@logfs.org
Cc: Prasad Joshi prasadjoshi.li...@gmail.com
---
block/blk-flush.c | 19 +--
fs/logfs/dev_bdev.c | 8 +---
2 files
Remove unnecessary operation and make the cmpxchg(lock, node, NULL) == node
check in mcs_spin_unlock() likely() as it is likely that a race did not occur
most of the time.
Also add in more comments describing how the local node is used in MCS locks.
Reviewed-by: Paul E. McKenney
In this patch series, we separated out the MCS lock code which was previously
embedded in the
mutex.c. This allows for easier reuse of MCS lock in other places like rwsem
and qrwlock.
We also did some micro optimizations and barrier cleanup.
This patches were previously part of the rwsem
This replaces some of the code that was in __bio_map_user_iov(), and
soon we're going to use this helper in the dio code.
Note that this relies on the recent change to make
generic_make_request() take arbitrary sized bios - we're not using
bio_add_page() here.
Signed-off-by: Kent Overstreet
This patch corrects the way memory barriers are used in the MCS lock
and removes ones that are not needed. Also add comments on all barriers.
Reviewed-by: Paul E. McKenney paul...@linux.vnet.ibm.com
Reviewed-by: Tim Chen tim.c.c...@linux.intel.com
Signed-off-by: Jason Low jason.l...@hp.com
---
We will need the MCS lock code for doing optimistic spinning for rwsem.
Extracting the MCS code from mutex.c and put into its own file allow us
to reuse this code easily for rwsem.
Reviewed-by: Ingo Molnar mi...@elte.hu
Reviewed-by: Peter Zijlstra pet...@infradead.org
Signed-off-by: Tim Chen
The following changes are made to enable mcs_spinlock.h file to be
widely included in other files without causing problem:
1) Include a number of prerequisite header files and define
arch_mutex_cpu_relax(), if not previously defined.
2) Separate out mcs_spin_lock() into a mcs_spinlock.c file.
So we get to delete our hacky workaround.
Signed-off-by: Kent Overstreet k...@daterainc.com
---
drivers/md/bcache/bcache.h| 18
drivers/md/bcache/io.c| 100 +-
drivers/md/bcache/journal.c | 4 +-
drivers/md/bcache/request.c |
generic_make_request() will now do for us what the code in blk-lib.c was
doing manually, with the bio_batch stuff - we still need some looping in
case we're trying to discard/zeroout more than around a gigabyte, but
when we can submit that much at a time doing the submissions in parallel
really
We get a measurable performance increase by handling this in the driver when
we're already looping over the biovec, instead of handling it separately in
generic_make_request() (or bio_add_page() originally)
Signed-off-by: Kent Overstreet k...@daterainc.com
---
drivers/block/mtip32xx/mtip32xx.c |
With immutable biovecs we don't want code accessing bi_io_vec directly -
the uses this patch changes weren't incorrect since they all own the
bio, but it makes the code harder to audit for no good reason - also,
this will help with multipage bvecs later.
Signed-off-by: Kent Overstreet
Next patch is going to make generic_make_request() handle arbitrary
sized bios by splitting them if necessary. It makes more sense to call
blk_queue_bounce() first, partly so it's working on larger bios - but also the
code that splits bios, and __blk_recalc_rq_segments(), won't have to take into
The way the block layer is currently written, it goes to great lengths
to avoid having to split bios; upper layer code (such as bio_add_page())
checks what the underlying device can handle and tries to always create
bios that don't need to be split.
But this approach becomes unwieldy and
701 - 800 of 1126 matches
Mail list logo