On Wed, Feb 20, 2013 at 04:04:41PM -0600, Seth Jennings wrote:
> diff --git a/mm/zsmalloc.c b/mm/zsmalloc.c
> +#define MAX(a, b) ((a) >= (b) ? (a) : (b))
> +/* ZS_MIN_ALLOC_SIZE must be multiple of ZS_ALIGN */
> +#define ZS_MIN_ALLOC_SIZE \
> + MAX(32, (ZS_MAX_PAGES_PER_ZSPAGE << PAGE_SHIFT >>
In many cases, documentation around composite drivers suggest
setting the idVendor and other module params as follows:
$ insmod g_ffs.ko idVendor= iSerialNumber=
However, this won't work if the driver is not compiled in as a
module, as the module_param permissions are S_IRUGO.
Thus this patch
On Wed, 20 Feb 2013 19:48:34 -0800
"Darrick J. Wong" wrote:
> > I grabbed the patches. They should appear in linux-next tomorrow if I
> > can get the current pooppile to build.
>
> Well... these patches have been banging around in -next for a month or so now.
> As far as I know there haven't
On Thu, Feb 21, 2013 at 02:32:43PM -0800, Andrew Morton wrote:
> On Wed, 20 Feb 2013 19:48:34 -0800
> "Darrick J. Wong" wrote:
>
> > > I grabbed the patches. They should appear in linux-next tomorrow if I
> > > can get the current pooppile to build.
> >
> > Well... these patches have been
On Thu, Feb 21, 2013 at 02:18:41PM -0800, Andrew Morton wrote:
> On Thu, 21 Feb 2013 12:00:28 +0400
> Cyrill Gorcunov wrote:
>
> > From: Amnon Shiloh
> > Subject: prctl: Make PR_SET_MM being depend on own CONFIG_MM_FIELDS_SETTING
> >
> > ...
> >
> > Signed-off-by: Amnon Shiloh
>
> The "..."
On Thu, 21 Feb 2013 16:21:37 -0600
Seth Jennings wrote:
> On 02/21/2013 02:36 PM, Cody P Schafer wrote:
> > On Wed, Feb 20, 2013 at 04:04:41PM -0600, Seth Jennings wrote:
> >> diff --git a/mm/zsmalloc.c b/mm/zsmalloc.c
> >> +#define MAX(a, b) ((a) >= (b) ? (a) : (b))
> >> +/* ZS_MIN_ALLOC_SIZE
On 20 February 2013 14:19, Mark Brown
wrote:
> On Fri, Feb 15, 2013 at 12:56:32PM +, Lee Jones wrote:
>
>> +static int ab8500_gpadc_suspend(struct device *dev)
>> +{
>> + struct ab8500_gpadc *gpadc = dev_get_drvdata(dev);
>> +
>> + mutex_lock(>ab8500_gpadc_lock);
>> +
>> +
On Thursday, February 21, 2013 10:39:40 AM Toshi Kani wrote:
> On Thu, 2013-02-21 at 16:52 +0100, Rafael J. Wysocki wrote:
> > From: Rafael J. Wysocki
> :
> >
> > This update fixes an issue pointed out by Toshi Kani (_OST shouldn't be
> > evaluated after successful _EJ0).
> >
> > Thanks,
> >
Nothing outside of the timekeeping core needs that lock.
Signed-off-by: Thomas Gleixner
---
include/linux/jiffies.h |1 -
kernel/time/tick-internal.h |2 ++
kernel/time/timekeeping.c |1 +
3 files changed, 3 insertions(+), 1 deletion(-)
Index:
We want to shorten the seqcount write hold time. So split the seqlock
into a lock and a seqcount.
Open code the seqwrite_lock in the places which matter and drop the
sequence counter update where it's pointless.
Signed-off-by: Thomas Gleixner
---
kernel/time/timekeeping.c | 118
Calculate the cycle interval shifted value once. No functional change,
just makes the code more readable.
Signed-off-by: Thomas Gleixner
---
kernel/time/timekeeping.c |7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
Index: linux-2.6/kernel/time/timekeeping.c
Shorten the seqcount write hold region to the actual update of the
timekeeper and the related data (e.g vsyscall).
On a contemporary x86 system this reduces the maximum latencies on
Preempt-RT from 8us to 4us on the non-timekeeping cores.
Signed-off-by: Thomas Gleixner
---
Use the shadow timekeeper to do the update_wall_time() adjustments and
then copy it over to the real timekeeper.
Keep the shadow timekeeper in sync when updating stuff outside of
update_wall_time().
This allows us to limit the timekeeper_seq hold time to the update of
the real timekeeper and the
For calculating the new timekeeper values store the new cycle_last
value in the timekeeper and update the clock->cycle_last just when we
actually update the new values.
Signed-off-by: Thomas Gleixner
---
kernel/time/timekeeping.c |4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
For implementing a shadow timekeeper and a split calculation/update
region we need to store the cycle_last value in the timekeeper and
update the value in the clocksource struct only in the update region.
Add the extra storage to the timekeeper.
Signed-off-by: Thomas Gleixner
---
On Thu, Feb 21 2013, John Stultz wrote:
> In many cases, documentation around composite drivers suggest
> setting the idVendor and other module params as follows:
>
> $ insmod g_ffs.ko idVendor= iSerialNumber=
>
> However, this won't work if the driver is not compiled in as a
> module, as the
The vsyscall based timekeeping interfaces for userspace provide the
shortest possible reader side blocking (update of the vsyscall gtod
data structure), but the kernel side interfaces to timekeeping are
blocked over the full code sequence of calculating update_wall_time()
magic which can be rather
Make the lock a separate entity. Preparatory patch for shadow
timekeeper structure.
Signed-off-by: Thomas Gleixner
---
include/linux/timekeeper_internal.h |2
kernel/time/timekeeping.c | 96 +---
2 files changed, 47 insertions(+), 51 deletions(-)
From: Rafael J. Wysocki
Multiple drivers handling hotplug-capable ACPI device nodes install
notify handlers covering the same types of events in a very similar
way. Moreover, those handlers are installed in separate namespace
walks, although that really should be done during namespace scans
On Thu, 2013-02-21 at 22:51 +, Thomas Gleixner wrote:
> Now the obvious question whether this is worth the trouble can be
> answered easily. Preempt-RT users and HPC folks have complained about
> the long write hold time of the timekeeping seqcount since years and a
> quick test on a
On Tue, Feb 19, 2013 at 04:21:28PM -0800, Tejun Heo wrote:
> On Tue, Feb 19, 2013 at 4:17 PM, Minchan Kim wrote:
> > Should we really enable memcg for just pressure notificaion in embedded
> > side?
> > I didn't check the size(cgroup + memcg) and performance penalty but I don't
> > want
> > to
This series is an attempt to define a common way for devicetree
initialized power_supplies to define their list of supplicants
in a common manner.
Instead of relying on custom properties which contain is list of
strings, use the much more direct method of phandles to reference
the supplies and
With the growing support for dt, it make sense to try to make use of
dt features to make the general code cleaner. This patch is an
attempt to commonize how chargers and their supplies are linked.
Following common dt convention, the "supplied-to" char** list is
replaced with phandle lists defined
This property is meant to be used in device nodes which represent
power_supply devices that wish to provide a list of supplies to
which they provide power. A common case is a AC Charger with
the batteries it powers.
Signed-off-by: Rhyland Klein
---
v2:
- Changed property to "power-supply"
With the addition of the device_nodes to use to link suppliers and
supplicants, its useful to add logic to handle the creation of
the list in a common place so as to be common for all drivers.
As of now, as long as the supply's device_node is supplied, the core
will attempt to parse the list of
Hi,
On Thu, 21 Feb 2013 13:07:56 +0530 Vineet Gupta
wrote:
>
> >> I guess you'll have to do something similar for arch/metag, and Vineet
> >> will do it for arch/arc.
>
> After getting the tip-bot msg about Stephen's patch for -mm, I never saw it in
> -next and thus was not sure how when it
On Thu, Feb 21, 2013 at 10:19:48PM +, Heasley, Seth wrote:
> Hi Neil,
>
> >> This patch adds the iSMT SMBus Controller DeviceIDs for the Intel Avoton
> >SOC.
> >>
> >> Signed-off-by: Seth Heasley
> >Is there a part number (I.e. S1200) that we can use in the name, rather than
> >the project
On Monday, February 11, 2013 01:20:00 PM Viresh Kumar wrote:
> Currently, there can't be multiple instances of single governor_type. If we
> have
> a multi-package system, where we have multiple instances of struct policy (per
> package), we can't have multiple instances of same governor. i.e. We
On 02/21/2013 02:52 PM, Michal Nazarewicz wrote:
On Thu, Feb 21 2013, John Stultz wrote:
In many cases, documentation around composite drivers suggest
setting the idVendor and other module params as follows:
$ insmod g_ffs.ko idVendor= iSerialNumber=
However, this won't work if the driver is
On Tue, Feb 19, 2013 at 01:50:55PM -0500, Waiman Long wrote:
> It was found that the Oracle database software issues a lot of call
> to the seq_path() kernel function which translates a (dentry, mnt)
> pair to an absolute path. The seq_path() function will eventually
> take the following two
On Monday, February 11, 2013 01:20:03 PM Viresh Kumar wrote:
> We don't need to keep two structures for file attributes, global_attr and
> freq_attr. Lets use freq_attr only for cpufreq core and drivers.
>
> Signed-off-by: Viresh Kumar
> ---
> drivers/cpufreq/acpi-cpufreq.c | 9 -
>
On Monday, February 11, 2013 01:20:02 PM Viresh Kumar wrote:
> have_multiple_policies is required by platforms having multiple clock-domains
> for cpus, i.e. supporting multiple policies for cpus. This patch adds in a
> Kconfig option for enabling execution of this code.
>
> Reported-by: Borislav
> On 02/21/2013 02:52 PM, Michal Nazarewicz wrote:
>> If the driver is not compiled as a module, setting those variables
>> won't work anyway. Or am I missing something?
On Fri, Feb 22 2013, John Stultz wrote:
> Huh. It worked in my testing. But maybe that's only the first time its
> set? I'll
>
> | radeon :01:00.0: No connectors reported connected with modes
> | [drm] Cannot find any crtc or sizes - going 1024x768
>
> The connector is definitely connected, since this is a laptop with a
> built-in screen...
>
Can you get the log with drm.debug=6 from both boots as well?
Dave.
--
Hi Anton,
On Thu, Feb 21, 2013 at 03:04:26PM -0800, Anton Vorontsov wrote:
> On Tue, Feb 19, 2013 at 04:21:28PM -0800, Tejun Heo wrote:
> > On Tue, Feb 19, 2013 at 4:17 PM, Minchan Kim wrote:
> > > Should we really enable memcg for just pressure notificaion in embedded
> > > side?
> > > I
Just booted linus head on one of my old kvm based testing systems and
got the following splat:
[0.531910] BUG: unable to handle kernel NULL pointer dereference at
0024
[0.532173] IP: [] apei_hest_parse+0xd2/0xf0
[0.532173] PGD 0
[0.532173] Oops: [#1] PREEMPT SMP
On 02/18/2013 12:14 PM, Tanaka Takahisa wrote:
Hi Joseph,
Thanks a lot for your help.
The bug report tested a kernel with the patches. However, he reports the kernel
panic still occurs[0].
I understood. I guess this problem conflicts with the watchdog MMIO
address (*) written in SB700
On Friday, February 22, 2013 12:56:01 AM Thomas Gleixner wrote:
> Just booted linus head on one of my old kvm based testing systems and
> got the following splat:
>
> [0.531910] BUG: unable to handle kernel NULL pointer dereference at
> 0024
> [0.532173] IP: []
Dave Chinner writes:
> On Tue, Feb 19, 2013 at 01:50:55PM -0500, Waiman Long wrote:
>> It was found that the Oracle database software issues a lot of call
>> to the seq_path() kernel function which translates a (dentry, mnt)
>> pair to an absolute path. The seq_path() function will eventually
>>
Jeremy Allison wrote:
> On Thu, Feb 21, 2013 at 01:51:53PM +, Myklebust, Trond wrote:
> > On Thu, 2013-02-21 at 12:37 +0100, Ric Wheeler wrote:
> > > We have debated the need to have a system call to allow for offloading
> > > copy
> > > operations, for example to an NFS server (part to the
ping? any comments?
On Thu, Dec 20, 2012 at 10:43 PM, wrote:
> From: Zhi Yong Wu
>
> HI, guys,
>
> This patchset has been done scalability or performance tests
> by fs_mark, ffsb and compilebench.
> I have done the perf testing on Linux 3.7.0-rc8+ with Intel(R) Core(TM)
> i7-3770 CPU @
Hi Linus,
This is a corrected attempt at the x86/cpu branch, this time with the
fixes in that makes it not break on KVM (current or past), or any
other virtualizer which traps on this configuration.
Again, the biggest change here is enabling the WC+ memory type on AMD
processors, if the BIOS
On Thu, 2013-02-21 at 09:04 -0300, Mauro Carvalho Chehab wrote:
> Em Thu, 21 Feb 2013 09:26:07 +0800
> Huang Ying escreveu:
>
> > Sorry for late!
>
> Thanks for your comments. See my answers below.
> >
> > On Fri, 2013-02-15 at 10:44 -0200, Mauro Carvalho Chehab wrote:
> > > In order to allow
On Thu, Feb 21, 2013 at 1:12 PM, Arnd Bergmann wrote:
>
> The merge conflicts I mention in the tags are all for conflicts
> between the arm-soc branches. There are a few more conflicts
> with other stuff you already pulled, but it all looks simple
> as well. I have uploaded a 'for-linus' branch
Hi all,
Today's linux-next merge of the infiniband tree got a conflict in
drivers/infiniband/ulp/ipoib/ipoib_ethtool.c between commit 7826d43f2db4
("ethtool: fix drvinfo strings set in drivers") from the tree and commit
4b48680b5572 ("IPoIB: Add version and firmware info to ethtool
reporting")
From: Graeme Gregory
Number of voltages for SMPS regulators was off by one.
Signed-off-by: Graeme Gregory
Signed-off-by: Ian Lartey
---
drivers/regulator/palmas-regulator.c |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/drivers/regulator/palmas-regulator.c
From: Graeme Gregory
Read the chip varient and the OTP information from the chip and display
this on probe to aid in debugging of issues.
Older palmas chips do not have the USB_ID programmed and will therefore
return 0x for this field.
Signed-off-by: Graeme Gregory
Signed-off-by: Ian
Dear Andrew,
The code in "kernel/sys.c" that is currently within
CONFIG_CHECKPOINT_RESTORE is in fact, as I explain below,
one possible solution to a general issue, required by a wide
class of applications. It just so happened that the CRIU group
were the first to place this, or an equivalent
On Tue, Feb 19, 2013 at 01:11:51PM -0700, Alex Williamson wrote:
> On Tue, 2013-02-19 at 18:38 +1100, David Gibson wrote:
> > On Mon, Feb 18, 2013 at 10:24:00PM -0700, Alex Williamson wrote:
> > > On Mon, 2013-02-18 at 17:15 +1100, Alexey Kardashevskiy wrote:
[snip]
> > > Adding the window size
On Fri, 2013-02-22 at 00:06 +0100, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> Multiple drivers handling hotplug-capable ACPI device nodes install
> notify handlers covering the same types of events in a very similar
> way. Moreover, those handlers are installed in separate namespace
On Thu, Feb 21, 2013 at 4:15 PM, Rafael J. Wysocki wrote:
> On Friday, February 22, 2013 12:56:01 AM Thomas Gleixner wrote:
>> Just booted linus head on one of my old kvm based testing systems and
>> got the following splat:
>>
>> [0.531910] BUG: unable to handle kernel NULL pointer
If kimage_normal_alloc() fails to initialize an allocated kimage, it will free
the image but would still set 'rimage', as a result kexec_load will try
to free it again.
This would explode as part of the freeing process is accessing internal
members which point to uninitialized memory.
> -Original Message-
> From: Zach Brown [mailto:z...@redhat.com]
> Sent: Thursday, February 21, 2013 5:25 PM
> To: Myklebust, Trond
> Cc: Paolo Bonzini; Ric Wheeler; Linux FS Devel; linux-kernel@vger.kernel.org;
> Chris L. Mason; Christoph Hellwig; Alexander Viro; Martin K. Petersen;
>
On Thu, Feb 21, 2013 at 09:56:54AM +0100, Ingo Molnar wrote:
>
> * Shuah Khan wrote:
>
> > On Tue, Feb 19, 2013 at 7:27 PM, Linux Kernel Mailing List
> > wrote:
> > > Gitweb:
> > > http://git.kernel.org/linus/;a=commit;h=c3c186403c6abd32e719f005f0af950155a9e54d
> > > Commit:
On Thursday, February 21, 2013 05:23:19 PM Yinghai Lu wrote:
> On Thu, Feb 21, 2013 at 4:15 PM, Rafael J. Wysocki wrote:
> > On Friday, February 22, 2013 12:56:01 AM Thomas Gleixner wrote:
> >> Just booted linus head on one of my old kvm based testing systems and
> >> got the following splat:
>
Hi,
Those are based on tip:/irq/urgent. I'm pretty confident about the
1st patch. The 2nd patch passed through some discussions with Thomas:
it's a nice cleanup but it involves a small unfortunate workaround,
so I tagged it as an RFC. I have mixed feelings about it.
Thanks.
Frederic Weisbecker
The IRQ_EXIT_OFFSET trick was used to make sure the irq
doesn't get preempted after we substract the HARDIRQ_OFFSET
until we are entirely done with any code in irq_exit().
This workaround was necessary because some archs may call
irq_exit() with irqs enabled and there is still some code
in the
The irq code is run under HARDIRQ_OFFSET preempt offset until
we reach the softirq code. Then it's substracted, leaving the
preempt count to 0, whether we have pending softirqs or not.
Afterward, if we have softirqs to run, we'll run them under
the SOFTIRQ_OFFSET then set the preempt offset back
Hello Seungwon,
OK, I will change the commit message. And I also think Alim's idea is
good but need more detail about functional features of Synopsis' IP.
Similar situation would be happened to Exynos4210 which is not
supported by dw_mmc-exynos.c yet.
Regards,
Dongjin.
On Thu, Feb 21, 2013 at
On Thursday, February 21, 2013 06:12:21 PM Toshi Kani wrote:
> On Fri, 2013-02-22 at 00:06 +0100, Rafael J. Wysocki wrote:
> > From: Rafael J. Wysocki
> >
> > Multiple drivers handling hotplug-capable ACPI device nodes install
> > notify handlers covering the same types of events in a very
On Thu, 2013-02-21 at 13:54 -0800, David Rientjes wrote:
> On Tue, 5 Feb 2013, Mimi Zohar wrote:
>
> > diff --git a/security/integrity/ima/ima_policy.c
> > b/security/integrity/ima/ima_policy.c
> > index 4adcd0f..23f49e3 100644
> > --- a/security/integrity/ima/ima_policy.c
> > +++
On Wed, Feb 20, 2013 at 9:17 PM, Jingoo Han wrote:
> samsung-fb updates for the v3.9:
Ok, there's a good gpg signed tag now, with a very recent gpg key. Try
to get that key signed by a few people.
Anyway, I pulled, and noticed that I had gotten these patches through
Andrew, so then I undid my
On Wed, Feb 20, 2013 at 9:20 PM, Jingoo Han wrote:
>
> git://github.com/jingoo/linux.git tags/exynos-dp-3.9
Ok, Andrew seems to have taken these patches too, so I got them through him.
Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body
Sasha Levin writes:
> If kimage_normal_alloc() fails to initialize an allocated kimage, it will free
> the image but would still set 'rimage', as a result kexec_load will try
> to free it again.
>
> This would explode as part of the freeing process is accessing internal
> members which point to
On 21 February 2013 23:09, Stratos Karafotis wrote:
> Thanks again. Following V3 with your suggestion.
>
> Regards,
> Stratos
>
> ---8<
> Instead of checking only the absolute value of CPU load_freq to increase
> frequency, we detect
On 22 February 2013 05:05, Rafael J. Wysocki wrote:
> On Monday, February 11, 2013 01:20:00 PM Viresh Kumar wrote:
>> This patch is inclined towards providing this infrastructure. Because we are
>> required to allocate governor's resources dynamically now, we must do it at
>> policy creation and
On Friday, February 22, 2013 02:40:58 AM Rafael J. Wysocki wrote:
> On Thursday, February 21, 2013 05:23:19 PM Yinghai Lu wrote:
> > On Thu, Feb 21, 2013 at 4:15 PM, Rafael J. Wysocki wrote:
> > > On Friday, February 22, 2013 12:56:01 AM Thomas Gleixner wrote:
> > >> Just booted linus head on one
On Thursday, February 21, 2013 5:48 PM, Igor Grinberg wrote:
>
> On 02/21/13 10:31, Jingoo Han wrote:
> > Using gpio_request_one() can make the code simpler because it can
> > set the direction and initial value in one shot.
>
> If you are on this, then I think converting to gpio_request_array()
On 22 February 2013 05:23, Rafael J. Wysocki wrote:
> On Monday, February 11, 2013 01:20:02 PM Viresh Kumar wrote:
>> +config CPU_FREQ_HAVE_MULTIPLE_POLICIES
>> + bool
>> +
>
> So I suppose some architectures will select this, right?
Yes. And they have to enable have_multiple_policies too
On Friday, February 22, 2013 07:38:12 AM Viresh Kumar wrote:
> On 22 February 2013 05:05, Rafael J. Wysocki wrote:
> > On Monday, February 11, 2013 01:20:00 PM Viresh Kumar wrote:
>
> >> This patch is inclined towards providing this infrastructure. Because we
> >> are
> >> required to allocate
On 22 February 2013 05:15, Rafael J. Wysocki wrote:
> Why did you change all of the lines of this macro instead of changing just the
> one line you needed to change?
I didn't like the indentation used within the macro. So did it.
> Please don't do that.
Okay.
--
To unsubscribe from this list:
Using gpio_request_array()/gpio_free_array() can make the code
simpler because it can set the direction and initial value
in one shot and the for loop is unnecessary.
Also, struct v3020_gpio is removed, because the struct v3020_gpio
is replaced with struct gpio.
Signed-off-by: Jingoo Han
---
On 22 February 2013 07:51, Rafael J. Wysocki wrote:
> On Friday, February 22, 2013 07:38:12 AM Viresh Kumar wrote:
>> No. These are used atleast for ondemand & conservative.
>
> They will be after the next patch, you mean? :-)
> Well, it appeared so from the next patch ...
Yes :)
--
To
Grant, will you be able to include these for 3.9? They fix code that
you merged recently, so I'd be glad if they could be squashed into the
patch mentioned in the description.
Thanks,
Alex.
On Fri, Feb 15, 2013 at 2:46 PM, Alexandre Courbot wrote:
> This short series is a fixup to patch 6/9 of
On Friday, February 22, 2013 07:44:23 AM Viresh Kumar wrote:
> On 22 February 2013 05:23, Rafael J. Wysocki wrote:
> > On Monday, February 11, 2013 01:20:02 PM Viresh Kumar wrote:
>
> >> +config CPU_FREQ_HAVE_MULTIPLE_POLICIES
> >> + bool
> >> +
> >
> > So I suppose some architectures will
On 11 February 2013 13:20, Viresh Kumar wrote:
> diff --git a/include/linux/cpufreq.h b/include/linux/cpufreq.h
> #define CPUFREQ_PRECHANGE (0)
> @@ -183,11 +197,10 @@ static inline unsigned long cpufreq_scale(unsigned long
> old, u_int div, u_int mu
> #define CPUFREQ_GOV_STOP 2
>
On Thu, Feb 21, 2013 at 9:37 AM, Mark Lord wrote:
> On 13-02-20 10:05 PM, Linus Torvalds wrote:
>> On Wed, Feb 20, 2013 at 2:09 PM, David Miller wrote:
>>>
>>> 15) Orphan and delete a bunch of pre-historic networking drivers from
>>> Paul Gortmaker.
>>
>> Nooo You killed the 3c501 and
On Friday, February 22, 2013 07:47:44 AM Viresh Kumar wrote:
> On 22 February 2013 05:15, Rafael J. Wysocki wrote:
> > Why did you change all of the lines of this macro instead of changing just
> > the
> > one line you needed to change?
>
> I didn't like the indentation used within the macro.
On 22 February 2013 05:05, Rafael J. Wysocki wrote:
> Why don't you use different values here?
>
> If you need only one value, one #define should be sufficient.
This is the fixup i have for this, I will push all patches again to
cpufreq-for-3.10 branch:
On 22 February 2013 08:03, Rafael J. Wysocki wrote:
> On Friday, February 22, 2013 07:47:44 AM Viresh Kumar wrote:
>> On 22 February 2013 05:15, Rafael J. Wysocki wrote:
>> > Why did you change all of the lines of this macro instead of changing just
>> > the
>> > one line you needed to change?
On 02/21/2013 08:55 PM, ebied...@xmission.com wrote:
> Sasha Levin writes:
>
>> If kimage_normal_alloc() fails to initialize an allocated kimage, it will
>> free
>> the image but would still set 'rimage', as a result kexec_load will try
>> to free it again.
>>
>> This would explode as part of
On 02/21/2013 05:43 PM, Mike Galbraith wrote:
> On Thu, 2013-02-21 at 17:08 +0800, Michael Wang wrote:
>
>> But is this patch set really cause regression on your Q6600? It may
>> sacrificed some thing, but I still think it will benefit far more,
>> especially on huge systems.
>
> We spread on
Hi Wu,
Today's linux-next merge of the writeback tree got a conflict in
fs/btrfs/extent-tree.c between commit da633a421701 ("Btrfs: flush all
dirty inodes if writeback can not start") from the btrfs tree and commit
10ee27a06cc8 ("vfs: re-implement writeback_inodes_sb(_nr)_if_idle() and
rename
On 02/21/2013 06:20 PM, Peter Zijlstra wrote:
> On Thu, 2013-02-21 at 12:51 +0800, Michael Wang wrote:
>> The old logical when locate affine_sd is:
>>
>> if prev_cpu != curr_cpu
>> if wake_affine()
>> prev_cpu = curr_cpu
>> new_cpu =
Hi Linus,
The following changes since commit 19f949f52599ba7c3f67a5897ac6be14bfcb1200:
Linux 3.8 (2013-02-18 15:58:34 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/lliubbo/blackfin.git for-linus
for you to fetch changes up to
On 22 February 2013 07:59, Rafael J. Wysocki wrote:
> On Friday, February 22, 2013 07:44:23 AM Viresh Kumar wrote:
>> If you don't like this one then we can add another entry
>> into struct policy like: gov_sysfs_parent.
>
> I don't know. This is going to look kind of ugly this way or another I
On 11 February 2013 13:19, Viresh Kumar wrote:
> This is targetted for 3.10-rc1 or linux-next just after the merge window.
Hi Rafael,
I have pushed this patch again with the modifications/fixups i posted:
cpufreq-for-3.10
Also i have swapped patch 3 & 4, in case you decide to drop that Kconfig
On 02/21/2013 07:37 PM, Peter Zijlstra wrote:
> On Thu, 2013-02-21 at 12:58 +0800, Michael Wang wrote:
>>
>> You are right, it cost space in order to accelerate the system, I've
>> calculated the cost once before (I'm really not good at this, please
>> let
>> me know if I make any silly
On 02/21/2013 11:50 PM, Seth Jennings wrote:
On 02/21/2013 02:49 AM, Ric Mason wrote:
On 02/19/2013 03:16 AM, Seth Jennings wrote:
On 02/16/2013 12:21 AM, Ric Mason wrote:
On 02/14/2013 02:38 AM, Seth Jennings wrote:
This patch adds a documentation file for zsmalloc at
On 02/21/2013 11:50 PM, Seth Jennings wrote:
On 02/21/2013 02:49 AM, Ric Mason wrote:
On 02/19/2013 03:16 AM, Seth Jennings wrote:
On 02/16/2013 12:21 AM, Ric Mason wrote:
On 02/14/2013 02:38 AM, Seth Jennings wrote:
This patch adds a documentation file for zsmalloc at
于 2013年02月22日 09:55, Eric W. Biederman 写道:
> Sasha Levin writes:
>
>> If kimage_normal_alloc() fails to initialize an allocated kimage, it will
>> free
>> the image but would still set 'rimage', as a result kexec_load will try
>> to free it again.
>>
>> This would explode as part of the freeing
On Thu, 21 Feb 2013 11:40:54 -0500
Nicolas Pitre wrote:
> On Thu, 21 Feb 2013, Kim Phillips wrote:
>
> > On Wed, 20 Feb 2013 23:29:58 -0500
> > Nicolas Pitre wrote:
> >
> > > On Wed, 20 Feb 2013, Kim Phillips wrote:
> > >
> > > > On Wed, 20 Feb 2013 10:43:18 -0500
> > > > Nicolas Pitre
On 02/22/2013 12:06 AM, Srikar Dronamraju wrote:
> * Peter Zijlstra [2013-02-20 09:46:25]:
>
>> On Mon, 2013-02-18 at 18:31 +0530, Srikar Dronamraju wrote:
>>> pick_next_entity() prefers next, then last. However code checks if the
>>> left entity can be skipped even if next / last is set.
>>>
On 02/22/2013 05:42 AM, Dan Magenheimer wrote:
From: Ric Mason [mailto:ric.mas...@gmail.com]
Subject: Re: Questin about swap_slot free and invalidate page
On 02/19/2013 11:27 PM, Dan Magenheimer wrote:
From: Ric Mason [mailto:ric.mas...@gmail.com]
Hugh is right that handling the possibility
(2013/02/21 17:34), Glauber Costa wrote:
On 02/21/2013 03:00 AM, Tejun Heo wrote:
(cc'ing cgroup / memcg people and quoting whole body)
Looks like something is going wrong with memcg cache destruction.
Glauber, any ideas? Also, can we please not use names as generic as
On 02/22/2013 10:53 AM, Michael Wang wrote:
>> >
>>> >> And the final cost is 3000 int and 103 pointer, and some padding,
>>> >> but won't bigger than 10M, not a big deal for a system with 1000 cpu
>>> >> too.
>> >
>> > Maybe, but quadric stuff should be frowned upon at all times, these
>> >
On Thu, 21 Feb 2013, Kim Phillips wrote:
> Here's the asm version I'm working on now, based on compiler
> output of the C version. Haven't tested beyond defconfig builds,
> which pass ok.
>
> Is there anything I have to do for thumb mode? If so, how to test?
You just need to pick a config
On 02/21/2013 09:46 PM, Zhang Yanfei wrote:
> 于 2013年02月22日 09:55, Eric W. Biederman 写道:
>> Sasha Levin writes:
>>
>>> If kimage_normal_alloc() fails to initialize an allocated kimage, it will
>>> free
>>> the image but would still set 'rimage', as a result kexec_load will try
>>> to free it
On 02/21/2013 04:17 PM, Hugh Dickins wrote:
Here's a second KSM series, based on mmotm 2013-02-19-17-20: partly in
response to Mel's review feedback, partly fixes to issues that I found
myself in doing more review and testing. None of the issues fixed are
truly show-stoppers, though I would
Hi Andrew,
Today's linux-next merge of the akpm-current tree got a conflict in
fs/btrfs/inode.cfs/btrfs/file.c between commit 55e301fd57a6 ("Btrfs: move
fs/btrfs/ioctl.h to include/uapi/linux/btrfs.h") from the btrfs tree and
commit "aio: don't include aio.h in sched.h" from the akpm-current
1001 - 1100 of 1178 matches
Mail list logo
