Hello,
cc'ing Dhaval and Frederic. They were interested in the subject
before and Dhaval was pretty vocal about cpuacct having a separate
hierarchy (or at least granularity).
On Wed, Sep 05, 2012 at 12:04:47PM +0200, Peter Zijlstra wrote:
cpuacct is rather unique tho. I think it's gonna be
On Fri, Aug 31, 2012 at 1:39 AM, Michel Lespinasse wal...@google.com wrote:
On Fri, Aug 31, 2012 at 1:35 AM, Adrian Hunter adrian.hun...@intel.com
wrote:
On 31/08/12 11:15, Andrew Morton wrote:
On Fri, 31 Aug 2012 01:07:24 -0700 Michel Lespinasse wal...@google.com
wrote:
I thought Andrew
+* will probably be removed at some point in the future.
+*/
+ if (check_amd_hwpstate_cpu(0)) {
...
[ Linux-Next (next-20120906) ]
19 config X86_ACPI_CPUFREQ
20 tristate ACPI Processor P-States driver
21 select CPU_FREQ_TABLE
22 depends on ACPI_PROCESSOR
23
On Thu, Sep 06, 2012 at 08:21:50PM +0200, Peter Zijlstra wrote:
On Thu, 2012-09-06 at 10:46 -0700, Paul E. McKenney wrote:
Getting these
CPUs into adaptive-tick mode more quickly reduces OS jitter, which is
one big expected benefit of adaptive-tick mode.
I'm not sure I agree with that
Il 06/09/2012 20:52, Nicholas A. Bellinger ha scritto:
That way we can just disable a problematic fabric instead of having to
revert the whole thing if users run into problems with a specific fabric
module late during the cycle. If the other fabric maintainers are OK
with enabling this in
Let's wait once Dmitry is finished with the input changes, and I can
either take the set through my tree with his Signed-off-by: on the Input
patches, or vice-versa.
Ok. Meanwhile, the current set is now in a temporary branch on github,
see below. Given there are no more change requests, I
Il 06/09/2012 20:58, Nicholas A. Bellinger ha scritto:
On Thu, 2012-09-06 at 17:13 +0200, Paolo Bonzini wrote:
The purpose of this function is to clear a LUN set in the CDB, in case
the initiator talking to us is speaking an old standards version.
However, as things stand, pscsi_clear_cdb_lun
On Thu, Sep 06, 2012 at 04:38:32PM +0200, Peter Zijlstra wrote:
On Thu, 2012-08-30 at 11:56 -0700, Paul E. McKenney wrote:
+#ifdef CONFIG_PROVE_RCU_DELAY
+ udelay(10); /* Make preemption more probable. */
cond_resched(); /* for extra fun? */
The additional fun
on AMD CPUs for compatibility reasons and
+* only if configured. This is considered legacy code, which
+* will probably be removed at some point in the future.
+*/
+ if (check_amd_hwpstate_cpu(0)) {
...
[ Linux-Next (next-20120906) ]
19 config X86_ACPI_CPUFREQ
20
Ok, there's no line wrapping this time, so it applies.
However, your subject line is really too long, and you're missing a
description in the body of the patch. Did you lose the subject line
from the first version of the patch?
In general, subject lines shouldn't be longer than 50 characters,
On Thu, Sep 06, 2012 at 05:11:58PM +0200, Kurt Van Dijck wrote:
I also think that led triggers should be available.
Right, that's why I think the only way is to use device name.
yes, but it has 2 disadvantages:
* inconvenient. I like 'can0-tx' much more than any device name
(Sorry I
Il 06/09/2012 21:29, Nicholas A. Bellinger ha scritto:
On Thu, 2012-09-06 at 17:13 +0200, Paolo Bonzini wrote:
This patch started with the aim of fixing START STOP UNIT to a PSCSI
device. Right now, commands with a zero-size payload are skipped
completely. This is wrong; such commands should
On Thu, Sep 06, 2012 at 04:40:38PM +0200, Peter Zijlstra wrote:
On Thu, 2012-08-30 at 11:56 -0700, Paul E. McKenney wrote:
When rcu_preempt_offline_tasks() clears tasks from a leaf rcu_node
structure, it does not NULL out the structure's -boost_tasks field.
This commit therefore fixes this
On Wed, 2012-09-05 at 09:59 +0800, Fengguang Wu wrote:
Greetings,
This is possibly an aged warning.
if (!hardirq_count()) {
if (softirq_count()) {
/* like the above, but with softirqs */
=
There's a typo in $SUBJ.
On Wed, Sep 05, 2012 at 01:27:23PM -0700, Kent Overstreet wrote:
Now that bios keep track of where they were allocated from,
bio_integrity_alloc_bioset() becomes redundant.
+ Remove bio_integrity_alloc_bioset() and drop bio_set argument from
+ the related functions and
On Thu, Sep 06, 2012 at 04:51:18PM +0200, Peter Zijlstra wrote:
On Thu, 2012-08-30 at 11:56 -0700, Paul E. McKenney wrote:
From: Paul E. McKenney paul...@linux.vnet.ibm.com
The print_other_cpu_stall() function accesses a number of rcu_node
fields without protection from the -lock. In
* Peter Ujfalusi peter.ujfal...@ti.com [120906 05:13]:
Remove the use of set_hs_extmute callback and let the codec driver to
handle the extmute GPIO.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/mach-omap2/board-zoom-peripherals.c | 9 ++---
On Thu, Sep 06, 2012 at 05:19:18PM +0200, Peter Zijlstra wrote:
On Thu, 2012-09-06 at 11:07 -0400, Steven Rostedt wrote:
On Thu, 2012-09-06 at 16:56 +0200, Peter Zijlstra wrote:
On Thu, 2012-08-30 at 11:56 -0700, Paul E. McKenney wrote:
If a given CPU avoids the idle loop but also
On Thu, Sep 6, 2012 at 1:46 PM, Tejun Heo t...@kernel.org wrote:
Hello,
cc'ing Dhaval and Frederic. They were interested in the subject
before and Dhaval was pretty vocal about cpuacct having a separate
hierarchy (or at least granularity).
Really? Time just has _not_ borne out this
Commit 1f2bfbd00e466ff3489b2ca5cc75b1cccd14c123 (kbuild: link of
vmlinux moved to a script) introduced in v3.5-rc1 broke kallsyms on
architectures which have symbol prefixes.
The --symbol-prefix argument used to be added to the KALLSYMS command
line from the architecture Makefile, however this
in the future.
+*/
+ if (check_amd_hwpstate_cpu(0)) {
...
[ Linux-Next (next-20120906) ]
19 config X86_ACPI_CPUFREQ
20 tristate ACPI Processor P-States driver
21 select CPU_FREQ_TABLE
22 depends on ACPI_PROCESSOR
23 help
24
Calxeda highbank SATA phy has intermittent problems bringing up a link
with Gen3 drives. Retrying the phy hard reset can work-around this issue,
but each reset also disables spread spectrum support. The reset function
also needs to reprogram the phy to enable spread spectrum support.
Create a new
On Thursday, September 06, 2012, Daniel Lezcano wrote:
On 09/06/2012 10:04 PM, Rafael J. Wysocki wrote:
On Thursday, September 06, 2012, Daniel Lezcano wrote:
On 09/06/2012 09:54 AM, Daniel Lezcano wrote:
On 09/05/2012 03:41 PM, Rafael J. Wysocki wrote:
On Saturday, September 01, 2012,
code, which
+* will probably be removed at some point in the future.
+*/
+ if (check_amd_hwpstate_cpu(0)) {
...
[ Linux-Next (next-20120906) ]
19 config X86_ACPI_CPUFREQ
20 tristate ACPI Processor P-States driver
21 select CPU_FREQ_TABLE
22
On Thursday, September 06, 2012, Sedat Dilek wrote:
On Thu, Sep 6, 2012 at 11:17 PM, Rafael J. Wysocki r...@sisk.pl wrote:
On Thursday, September 06, 2012, Sedat Dilek wrote:
[...]
Just wondering... Fell over it when digging into my boot-problem (this
appeared as a new Kconfig option,
* Paul E. McKenney (paul...@linux.vnet.ibm.com) wrote:
On Thu, Sep 06, 2012 at 04:36:02PM +0200, Peter Zijlstra wrote:
On Thu, 2012-08-30 at 11:18 -0700, Paul E. McKenney wrote:
From: Paul E. McKenney paul.mcken...@linaro.org
The current quiescent-state detection algorithm is
Added tty_device_create_release() and bound to dev-release in
tty_register_device_attr().
Added tty_port_register_device_attr() and used in uart_add_one_port()
instead of tty_register_device_attr().
Signed-off-by: Tomas Hlavacek tmshl...@gmail.com
---
drivers/tty/serial/serial_core.c |8
On Thu, Sep 06, 2012 at 08:41:09PM +0200, Peter Zijlstra wrote:
On Thu, 2012-09-06 at 17:46 +0200, Jiri Olsa wrote:
The 'perf diff' and 'std/hist' code is now changed to allow computations
mentioned in the paper. Two of them are implemented within this patchset:
1) ratio differential
On Thursday, September 06, 2012, John Stultz wrote:
Jon Medhurst (Tixy) recently noticed a problem with the
events_lock usage. One of the Android patches that uses
wakeup_sources calls wakeup_source_add() with irqs disabled.
However, the event_lock usage in wakeup_source_add() uses
On Thu, Sep 06, 2012 at 05:00:29PM -0400, Steven Rostedt wrote:
On Wed, 2012-09-05 at 09:59 +0800, Fengguang Wu wrote:
Greetings,
This is possibly an aged warning.
if (!hardirq_count()) {
if (softirq_count()) {
/* like the above, but
Hello,
On Wed, Sep 05, 2012 at 12:07:24PM +0200, Lars Ellenberg wrote:
So reiterating the situation:
If I'd submit a non-empty bio with FLUSH/FUA set,
on a queue that does support flush, we get to
blk_queue_bio()
if (bio-bi_rw (REQ_FLUSH | REQ_FUA)) {
On Thu, Sep 06, 2012 at 05:18:59PM -0400, Mathieu Desnoyers wrote:
* Paul E. McKenney (paul...@linux.vnet.ibm.com) wrote:
On Thu, Sep 06, 2012 at 04:36:02PM +0200, Peter Zijlstra wrote:
On Thu, 2012-08-30 at 11:18 -0700, Paul E. McKenney wrote:
From: Paul E. McKenney
Since v8: Just a few minor comment/patch descriptions changes
Kent Overstreet (9):
block: Generalized bio pool freeing
block: Ues bi_pool for bio_integrity_alloc()
dm: Use bioset's front_pad for dm_rq_clone_bio_info
block: Add bio_reset()
pktcdvd: Switch to bio_kmalloc()
block: Add
Previously, bio_kmalloc() and bio_alloc_bioset() behaved slightly
different because there was some almost-duplicated code - this fixes
some of that.
The important change is that previously bio_kmalloc() always set
bi_io_vec = bi_inline_vecs, even if nr_iovecs == 0 - unlike
bio_alloc_bioset().
Previously, dm_rq_clone_bio_info needed to be freed by the bio's
destructor to avoid a memory leak in the blk_rq_prep_clone() error path.
This gets rid of a memory allocation and means we can kill
dm_rq_bio_destructor.
The _rq_bio_info_cache kmem cache is unused now and needs to be deleted,
but
Previously, there was bio_clone() but it only allocated from the fs bio
set; as a result various users were open coding it and using
__bio_clone().
This changes bio_clone() to become bio_clone_bioset(), and then we add
bio_clone() and bio_clone_kmalloc() as wrappers around it, making use of
the
Previously, bio_kmalloc() and bio_alloc_bioset() behaved slightly
different because there was some almost-duplicated code - this fixes
some of that.
The important change is that previously bio_kmalloc() always set
bi_io_vec = bi_inline_vecs, even if nr_iovecs == 0 - unlike
bio_alloc_bioset().
Previously, there was bio_clone() but it only allocated from the fs bio
set; as a result various users were open coding it and using
__bio_clone().
This changes bio_clone() to become bio_clone_bioset(), and then we add
bio_clone() and bio_clone_kmalloc() as wrappers around it, making use of
the
Now that we've got generic code for freeing bios allocated from bio
pools, this isn't needed anymore.
This patch also makes bio_free() static, since without bi_destructor
there should be no need for it to be called anywhere else.
bio_free() is now only called from bio_put, so we can refactor
Now that we've got generic code for freeing bios allocated from bio
pools, this isn't needed anymore.
This patch also makes bio_free() static, since without bi_destructor
there should be no need for it to be called anywhere else.
While we're at it, since bio_free() is now only called from one
Now that bios keep track of where they were allocated from,
bio_integrity_alloc_bioset() becomes redundant.
Remove bio_integrity_alloc_bioset() and drop bio_set argument from the
related functions and make them use bio-bi_pool.
Signed-off-by: Kent Overstreet koverstr...@google.com
CC: Jens Axboe
Reusing bios is something that's been highly frowned upon in the past,
but driver code keeps doing it anyways. If it's going to happen anyways,
we should provide a generic method.
This'll help with getting rid of bi_destructor - drivers/block/pktcdvd.c
was open coding it, by doing a bio_init()
This is prep work for killing bi_destructor - previously, pktcdvd had
its own pkt_bio_alloc which was basically duplication bio_kmalloc(),
necessitating its own bi_destructor implementation.
v5: Un-reorder some functions, to make the patch easier to review
Signed-off-by: Kent Overstreet
Reusing bios is something that's been highly frowned upon in the past,
but driver code keeps doing it anyways. If it's going to happen anyways,
we should provide a generic method.
This'll help with getting rid of bi_destructor - drivers/block/pktcdvd.c
was open coding it, by doing a bio_init()
With the old code, when you allocate a bio from a bio pool you have to
implement your own destructor that knows how to find the bio pool the
bio was originally allocated from.
This adds a new field to struct bio (bi_pool) and changes
bio_alloc_bioset() to use it. This makes various bio
On Thu, Sep 06, 2012 at 05:12:08PM +0200, Peter Zijlstra wrote:
On Thu, 2012-08-30 at 11:56 -0700, Paul E. McKenney wrote:
From: Paul E. McKenney paul.mcken...@linaro.org
The can_stop_idle_tick() function complains if a softirq vector is
raised too late in the idle-entry process,
Hi
On Thu, 6 Sep 2012, Felipe Balbi wrote:
Hi guys,
here's v4 of the omap uart patchset. No changes other than a rebase on top of
Greg's tty-next branch and Tony's Acked-by being added to a couple patches
Note: I'm resending the series with Vikram's Software Flow Control fix anyway
as
Hi Linus,
Here are some more fixes for v3.6. These all fix things we merged in
v3.6-rc1. Four are fixes for the D3cold support, and one is for a
boot lockup on PA Semi caused by a printk while the console BAR is
still disabled.
Bjorn
The following changes since commit
On Thu, 2012-09-06 at 14:03 -0700, Paul E. McKenney wrote:
Here are a few other ways that stalls can happen:
o A CPU looping in an RCU read-side critical section.
For a minute? That's a bug.
o A CPU looping with interrupts disabled. This condition can
result in
Hello!
On Thu, Sep 6, 2012 at 11:17 PM, Tomas Hlavacek tmshl...@gmail.com wrote:
Added tty_device_create_release() and bound to dev-release in
tty_register_device_attr().
Added tty_port_register_device_attr() and used in uart_add_one_port()
instead of tty_register_device_attr().
On Thu, 2012-09-06 at 14:29 -0700, Paul E. McKenney wrote:
Didn't we talk about having the rcu_dereference_raw() not do the check?
The function tracer is just too invasive to add work arounds to prevent
lockdep from screaming about it.
Actually, rcu_dereference_raw() is already
On Thu, 2012-09-06 at 14:35 -0700, Paul E. McKenney wrote:
But yes, RCU was a lot simpler before people started worrying about
its energy efficiency. ;-)
Tell them to buy bigger batteries.
-- Steve
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a
Felipe Balbi ba...@ti.com writes:
nobody needs to access the uart_omap_port structure
other than omap-serial.c file. Let's move that
structure definition to the C source file in order
to prevent anyone from accessing our structure.
Tested-by: Shubhrajyoti D shubhrajy...@ti.com
Acked-by:
On Thu, Sep 06, 2012 at 05:41:01PM -0400, Steven Rostedt wrote:
On Thu, 2012-09-06 at 14:03 -0700, Paul E. McKenney wrote:
Here are a few other ways that stalls can happen:
o A CPU looping in an RCU read-side critical section.
For a minute? That's a bug.
o A CPU looping
Stephen Warren wrote:
On 09/05/2012 12:20 AM, Thomas Abraham wrote:
Add a new device tree enabled pinctrl and gpiolib driver for Samsung
SoC's. This driver provides a common and extensible framework for all
Samsung SoC's to interface with the pinctrl and gpiolib subsystems. This
driver
On Thu, 2012-09-06 at 14:58 -0700, Paul E. McKenney wrote:
All these cases deserve a warning.
Agreed, and that is the whole purpose of the stall warnings.
Then let me ask the question again. According to the change log:
If a given CPU avoids the idle loop but also avoids starting a new
On Thu, Sep 06, 2012 at 05:56:39PM -0400, Steven Rostedt wrote:
On Thu, 2012-09-06 at 14:29 -0700, Paul E. McKenney wrote:
Didn't we talk about having the rcu_dereference_raw() not do the check?
The function tracer is just too invasive to add work arounds to prevent
lockdep from
On Thu, Sep 06, 2012 at 05:57:45PM -0400, Steven Rostedt wrote:
On Thu, 2012-09-06 at 14:35 -0700, Paul E. McKenney wrote:
But yes, RCU was a lot simpler before people started worrying about
its energy efficiency. ;-)
Tell them to buy bigger batteries.
If nuclear batteries are good
On Thu, Sep 06, 2012 at 06:05:53PM -0400, Steven Rostedt wrote:
On Thu, 2012-09-06 at 14:58 -0700, Paul E. McKenney wrote:
All these cases deserve a warning.
Agreed, and that is the whole purpose of the stall warnings.
Then let me ask the question again. According to the change log:
On 09/06/2012 07:31 PM, Steven Rostedt wrote:
On Thu, 2012-09-06 at 18:35 +0200, Toralf Förster wrote:
I filed a bug report
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54495
and got this answer :
--- Comment #1 from Hans-Peter Nilsson hp at gcc dot gnu.org 2012-09-05
22:14:00 UTC ---
On Thu, Sep 06, 2012 at 12:21:15PM +0900, Jun'ichi Nomura wrote:
On 09/06/12 05:27, Kent Overstreet wrote:
@@ -2718,7 +2705,8 @@ struct dm_md_mempools *dm_alloc_md_mempools(unsigned
type, unsigned integrity)
if (!pools-tio_pool)
goto free_io_pool_and_out;
-
On Thu, Sep 06, 2012 at 11:05:11AM +0800, Michael Wang wrote:
On 09/05/2012 09:55 PM, Christoph Lameter wrote:
On Wed, 5 Sep 2012, Michael Wang wrote:
Since the cachep and cachep-slabp_cache's l3 alien are in the same lock
class,
fake report generated.
Ahh... That is a key
Hi Arnd,
On Sat, Aug 18, 2012 at 3:08 PM, Arnd Bergmann a...@arndb.de wrote:
On Saturday 18 August 2012, Fabio Estevam wrote:
From: Fabio Estevam fabio.este...@freescale.com
commit 7c5763 (drivers:misc: Remove MISC_DEVICES config option) removed
CONFIG_MISC_DEVICES option, so remove the
Previously, dm_rq_clone_bio_info needed to be freed by the bio's
destructor to avoid a memory leak in the blk_rq_prep_clone() error path.
This gets rid of a memory allocation and means we can kill
dm_rq_bio_destructor.
The _rq_bio_info_cache kmem cache is unused now and needs to be deleted,
but
Reusing bios is something that's been highly frowned upon in the past,
but driver code keeps doing it anyways. If it's going to happen anyways,
we should provide a generic method.
This'll help with getting rid of bi_destructor - drivers/block/pktcdvd.c
was open coding it, by doing a bio_init()
Previously, there was bio_clone() but it only allocated from the fs bio
set; as a result various users were open coding it and using
__bio_clone().
This changes bio_clone() to become bio_clone_bioset(), and then we add
bio_clone() and bio_clone_kmalloc() as wrappers around it, making use of
the
Previously, bio_kmalloc() and bio_alloc_bioset() behaved slightly
different because there was some almost-duplicated code - this fixes
some of that.
The important change is that previously bio_kmalloc() always set
bi_io_vec = bi_inline_vecs, even if nr_iovecs == 0 - unlike
bio_alloc_bioset().
Now that we've got generic code for freeing bios allocated from bio
pools, this isn't needed anymore.
This patch also makes bio_free() static, since without bi_destructor
there should be no need for it to be called anywhere else.
bio_free() is now only called from bio_put, so we can refactor
On Fri, 17 Aug 2012 15:14:32 +0100
Mel Gorman mgor...@suse.de wrote:
If allocation fails after compaction then compaction may be deferred for
a number of allocation attempts. If there are subsequent failures,
compact_defer_shift is increased to defer for longer periods. This patch
uses that
Screwed up the bio_reset() patch in the last patch series when I went to edit
the description, fixed that here.
Only other change is the dm patch - made the front_pad conditional on
DM_TYPE_BIO_BASED.
Kent Overstreet (8):
block: Generalized bio pool freeing
block: Ues bi_pool for
This is prep work for killing bi_destructor - previously, pktcdvd had
its own pkt_bio_alloc which was basically duplication bio_kmalloc(),
necessitating its own bi_destructor implementation.
v5: Un-reorder some functions, to make the patch easier to review
Signed-off-by: Kent Overstreet
Now that bios keep track of where they were allocated from,
bio_integrity_alloc_bioset() becomes redundant.
Remove bio_integrity_alloc_bioset() and drop bio_set argument from the
related functions and make them use bio-bi_pool.
Signed-off-by: Kent Overstreet koverstr...@google.com
CC: Jens Axboe
With the old code, when you allocate a bio from a bio pool you have to
implement your own destructor that knows how to find the bio pool the
bio was originally allocated from.
This adds a new field to struct bio (bi_pool) and changes
bio_alloc_bioset() to use it. This makes various bio
On 09/07/2012 01:11 AM, Paul Turner wrote:
On Thu, Sep 6, 2012 at 1:46 PM, Tejun Heo t...@kernel.org wrote:
Hello,
cc'ing Dhaval and Frederic. They were interested in the subject
before and Dhaval was pretty vocal about cpuacct having a separate
hierarchy (or at least granularity).
On 09/07/2012 12:38 AM, Tejun Heo wrote:
Hello, Peter, Glauber.
(I'm gonna write up cgroup core todos which should explain / address
this issue too. ATM I'm a bit overwhelmed with stuff accumulated
while traveling.)
Yes, please.
While you rightfully claim that you explained it a couple
Felipe Balbi ba...@ti.com writes:
Hi guys,
here's v4 of the omap uart patchset. No changes other than a rebase on top of
Greg's tty-next branch and Tony's Acked-by being added to a couple patches
Note: I'm resending the series with Vikram's Software Flow Control fix anyway
as it can just
On Sat, 4 Aug 2012 12:01:27 +0800
Ming Lei ming@canonical.com wrote:
This patch introduces the three helpers below:
void device_cache_fw_images(void)
void device_uncache_fw_images(void)
void device_uncache_fw_images_delay(unsigned long)
CONFIG_PM=n:
Hello, Glauber.
On Thu, Sep 6, 2012 at 3:39 PM, Glauber Costa glom...@parallels.com wrote:
Yes, please.
While you rightfully claim that you explained it a couple of times, it
all seems to be quite fuzzy. I don't blame it on you: the current state
of the interface leads to this.
Heh, I drank
On 09/05/2012 06:01 PM, Mark Brown wrote:
On Tue, Sep 04, 2012 at 02:43:39PM -0600, Stephen Warren wrote:
From: Laxman Dewangan ldewan...@nvidia.com
Device have SYS rail which is always ON. It is system power bus. LDO5
and LDO_RTC get powered through this rail internally. Add support for
From: Gyungoh Yoo jack@maxim-ic.com
The MAX8907 is an I2C-based power-management IC containing voltage
regulators, a reset controller, a real-time clock, and a touch-screen
controller.
The original driver was written by:
* Gyungoh Yoo jack@maxim-ic.com
Various fixes and enhancements by:
On Fri, 24 Aug 2012 16:57:35 +0800
Alex Shi alex@intel.com wrote:
The flush tlb optimization code has logical issue on UV platform.
It doesn't flush the full range at all, since it simply
ignores its 'end' parameter (and hence also the all indicator)
in uv_flush_tlb_others() function.
Hello Linus,
Please git pull the following tag:
git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git
stable/for-linus-3.6-rc4-tag
Nothing controversial. Fix for the newer tlb flushing code;
an old fix for Xen-SWIOTLB that had been bouncing around until
we narrowed why it fixed it; and
On Thu, Sep 06, 2012 at 10:24:24AM +0100, Mel Gorman wrote:
On Thu, Sep 06, 2012 at 01:49:03PM +0900, Minchan Kim wrote:
__offline_isolated_pages
/*
* BUG_ON hit or offline page
* which is used by someone
*/
BUG_ON(!PageBuddy(page A));
offline_page calling
Hello Yasuaki,
On Thu, Sep 06, 2012 at 06:14:39PM +0900, Yasuaki Ishimatsu wrote:
Hi, Minchan,
2012/09/06 16:30, Minchan Kim wrote:
Hello Yasuaki,
On Thu, Sep 06, 2012 at 04:17:54PM +0900, Yasuaki Ishimatsu wrote:
Hi Minchan,
2012/09/06 14:16, Minchan Kim wrote:
Like below,
On Thu, Sep 06, 2012 at 09:46:50AM +0200, Paolo Bonzini wrote:
VIRTIO_BALLOON_F_MUST_TELL_HOST cannot be used properly because it is a
negative feature: it tells you that silent defalte is not supported.
Right now, QEMU refuses migration if the target does not support all the
features that
On 03/09/12 22:29, Axel Lin wrote:
Include linux/sizes.h to fix below build errors:
CC arch/arm/mach-ep93xx/adssphere.o
arch/arm/mach-ep93xx/adssphere.c: In function 'adssphere_init_machine':
arch/arm/mach-ep93xx/adssphere.c:32:49: error: 'SZ_32M' undeclared (first use
in this
On Thu, Sep 06, 2012 at 03:35:00PM -0700, Kent Overstreet wrote:
Now that we've got generic code for freeing bios allocated from bio
pools, this isn't needed anymore.
This patch also makes bio_free() static, since without bi_destructor
there should be no need for it to be called anywhere
Add IOMEM defines for the TS72xx VIRT_BASE defines to fix type
conversion warnings.
Signed-off-by: Ryan Mallon rmal...@gmail.com
---
diff --git a/arch/arm/mach-ep93xx/include/mach/ts72xx.h
b/arch/arm/mach-ep93xx/include/mach/ts72xx.h
index f1397a1..b30deb6 100644
---
On Thu, Sep 06, 2012 at 03:35:01PM -0700, Kent Overstreet wrote:
Previously, bio_kmalloc() and bio_alloc_bioset() behaved slightly
different because there was some almost-duplicated code - this fixes
some of that.
The important change is that previously bio_kmalloc() always set
bi_io_vec =
On Thu, Sep 06, 2012 at 03:35:02PM -0700, Kent Overstreet wrote:
Previously, there was bio_clone() but it only allocated from the fs bio
set; as a result various users were open coding it and using
__bio_clone().
This changes bio_clone() to become bio_clone_bioset(), and then we add
This patchset updates the ACPI system-level (ex. hotplug)
notify handling with a new .sys_notify interface. It provides
the following changes:
- Allow ACPI drivers to register their system-level (hotplug)
notify handlers to a new .sys_notify interface through their
acpi_driver table. This
Added a new .sys_notify interface, which allows ACPI drivers to
register their system-level (ex. hotplug) notify handlers through
their acpi_driver table. The global notify handler acpi_bus_notify()
is called for all system-level ACPI notifications, which is changed
to call an appropriate
Changed the ACPI memory hotplug driver to use .sys_notify. Removed
ACPI namespace walks and their call-back functions that register and
unregister the hotplug handler to all memory device objects through
acpi_[install|remove]_notify_handler().
Signed-off-by: Toshi Kani toshi.k...@hp.com
---
Changed the ACPI container driver to use .sys_notify. Removed
ACPI namespace walks and their call-back function that register
and unregister the hotplug handler to all container objects
through acpi_[install|remove]_notify_handler().
Signed-off-by: Toshi Kani toshi.k...@hp.com
---
Changed the ACPI processor driver to use .sys_notify. Removed
ACPI namespace walks and their call-back function that register
and unregister the hotplug handler to all processor objects
through acpi_[install|remove]_notify_handler().
Signed-off-by: Toshi Kani toshi.k...@hp.com
---
The mm-of-the-moment snapshot 2012-09-06-16-46 has been uploaded to
http://www.ozlabs.org/~akpm/mmotm/
mmotm-readme.txt says
README for mm-of-the-moment:
http://www.ozlabs.org/~akpm/mmotm/
This is a snapshot of my -mm patch queue. Uploaded at random hopefully
more than once a week.
You
Hello, guys.
(cc'ing Jens, Alasdair and Neil)
On Thu, Sep 06, 2012 at 03:34:54PM -0700, Kent Overstreet wrote:
Screwed up the bio_reset() patch in the last patch series when I went to edit
the description, fixed that here.
Only other change is the dm patch - made the front_pad conditional
On 08/16/2012 08:13 AM, Laxman Dewangan wrote:
Remove the support code which uses the legacy APB DMA driver
for accessing the SPI FIFO.
The driver will use the dmaengine based APB DMA driver for
accessing reqding/writing to SPI FIFO.
Signed-off-by: Laxman Dewangan ldewan...@nvidia.com
On 08/16/2012 08:13 AM, Laxman Dewangan wrote:
Remove the support code which uses the legacy APB DMA driver
for accessing the I2S FIFO.
The driver will use the dmaengine based APB DMA driver for
accessing reqding/writing to I2S FIFO.
Signed-off-by: Laxman Dewangan ldewan...@nvidia.com
Trivially initialize return codes with default values when
the variable is declared.
Signed-off-by: Davidlohr Bueso d...@gnu.org
---
kernel/sys.c |9 +++--
1 files changed, 3 insertions(+), 6 deletions(-)
diff --git a/kernel/sys.c b/kernel/sys.c
index 241507f..b3b2ef7 100644
---
1301 - 1400 of 1542 matches
Mail list logo
