The following patches update cpuinfo to print SoC
model name for ARM.
The first patch exactly makes needed changes for ARM
architecture and adds a common approach to show SoC name.
Second patch uses this approach for OMAP4 SoCs (as live
example).
Looks like there were few attempts to do similar
On Tue, 29 Jan 2013 10:58:20 +0800
fli24 wrote:
> At present, the timeout value for freezing tasks is fixed as 20s,
> which is too long for handheld device usage, especially for mobile
> phone.
>
> In order to improve user experience, we enable freeze timeout
> configuration through sysctl, so
Starting with win8, vmbus interrupts can be delivered on any VCPU in the guest
and furthermore can be concurrently active on multiple VCPUs. Support this
interrupt delivery model by setting up a separate IDT entry for Hyper-V vmbus.
interrupts. I would like to thank Jan Beulich and
Thomas
From: Olaf Hering <[mailto:o...@aepfle.de]>
Enable hyperv_clocksource only if its advertised as a feature.
XenServer 6 returns the signature which is checked in
ms_hyperv_platform(), but it does not offer all features. Currently the
clocksource is enabled unconditionally in
Xen emulates Hyper-V to host enlightened Windows. Looks like this
emulation may be turned on by default even for Linux guests. Check and
fail Hyper-V detection if we are on Xen.
Signed-off-by: K. Y. Srinivasan
---
arch/x86/kernel/cpu/mshyperv.c |7 +++
1 files changed, 7 insertions(+),
On Tue, 29 Jan 2013 14:14:14 +0800
xtu4 wrote:
> @@ -209,8 +209,17 @@ ssize_t seq_read(struct file *file, char __user
> *buf, size_t size, loff_t *ppos)
> if (m->count < m->size)
> goto Fill;
> m->op->stop(m, p);
> -kfree(m->buf);
> -m->buf =
This patch-set implements the functionality to deliver Hyper-V VMBUS interrupts
via
a special IDT entry. Xen emulates Hyper-V and we have added code in this
patch-set to
properly manage this emulation when Linux is running on Hyper-V.
K. Y. Srinivasan (2):
X86: Add a check to catch Xen
From: Stephen Warren
Silence the following:
net/wireless/nl80211.c: In function '__cfg80211_wdev_from_attrs.clone.119':
net/wireless/nl80211.c:57:6: warning: 'wdev_id' may be used uninitialized in
this function
... by always initializing wdev_id to zero. I assume that wiphy_idx and
ifidx are
From: Stephen Warren
Silence the following:
drivers/gpu/drm/drm_irq.c: In function 'drm_calc_vbltimestamp_from_scanoutpos':
drivers/gpu/drm/drm_irq.c:583:24: warning: 'mono_time_offset.tv64' may be used
uninitialized in this function
... by always initializing mono_time_offset to zero. In
From: Stephen Warren
This fixes:
fs/ext4/super.c: In function 'ext4_fill_super':
fs/ext4/super.c:4040:1: warning: label 'failed_mount8' defined but not used
This label is only jumped to by code under ifdef CONFIG_QUOTA, so only
define the label in that case too.
Signed-off-by: Stephen Warren
On Thu, 24 Jan 2013, Joonsoo Kim wrote:
> From: Joonsoo Kim
>
> A static mapped area is ARM-specific, so it is better not to use
> generic vmalloc data structure, that is, vmlist and vmlist_lock
> for managing static mapped area. And it causes some needless overhead and
> reducing this overhead
On Thu, 24 Jan 2013, Joonsoo Kim wrote:
> From: Joonsoo Kim
>
> In current implementation, we used ARM-specific flag, that is,
> VM_ARM_STATIC_MAPPING, for distinguishing ARM specific static mapped area.
> The purpose of static mapped area is to re-use static mapped area when
> entire physical
On Tue, 29 Jan 2013 10:33:48 -0500
Don Zickus wrote:
> --- a/kernel/watchdog.c
> +++ b/kernel/watchdog.c
> @@ -79,6 +79,14 @@ static int __init softlockup_panic_setup(char *str)
> }
> __setup("softlockup_panic=", softlockup_panic_setup);
>
> +static int __init watchdog_thresh_setup(char
On Wed, 2013-01-30 at 00:41 +0100, Peter Hüwe wrote:
> ---> is there a way to consolidate these functions into one function (which
> can operate on the different types) ? It's almost a bit like 'templates'.
> Maybe with some gcc extensions or kernel magic functions ?
Nothing wrong with a macro.
On Tuesday, January 29, 2013 4:42 PM, Peter Hüwe wrote:
> Hi,
>
> while analyzing the comedi drivers, I noticed that quite a lot of them use a
> more or less similar find_boardinfo function.
> The names and the exact implementation differ slightly, but in most cases it
> boils down to:
>
2013/01/29 21:30, Rafael J. Wysocki wrote:
On Tuesday, January 29, 2013 12:36:35 PM Rafael J. Wysocki wrote:
On Tuesday, January 29, 2013 11:20:44 AM Yasuaki Ishimatsu wrote:
Hi Rafael,
2013/01/28 22:01, Rafael J. Wysocki wrote:
From: Rafael J. Wysocki
Currently, the ACPI namespace
On Tue, Jan 29, 2013 at 4:44 PM, Bjorn Helgaas wrote:
> A bus_type has a list of devices (klist_devices), but the list and the
> subsys_private structure that contains it are not initialized until the
> bus_type is registered with bus_register().
>
> The panic/reboot path has fixups that look up
On Tue, Jan 29, 2013 at 3:02 PM, Deucher, Alexander
wrote:
>> -Original Message-
>> From: Shuah Khan [mailto:shuahk...@gmail.com]
>> Sent: Tuesday, January 29, 2013 4:40 PM
>> To: Deucher, Alexander
>> Cc: Linus Torvalds; Linux Kernel Mailing List
>> Subject: Re: Linux 3.8-rc4
>>
>> On
A bus_type has a list of devices (klist_devices), but the list and the
subsys_private structure that contains it are not initialized until the
bus_type is registered with bus_register().
The panic/reboot path has fixups that look up devices in pci_bus_type. If
we panic before registering
On 01:08-20130130, Ruslan Bilovol wrote:
> Hi,
>
> On Tue, Jan 29, 2013 at 6:02 PM, Nishanth Menon wrote:
> >
> > On 17:54-20130129, Ruslan Bilovol wrote:
> > > Hi,
> > >
> > > The following patches update cpuinfo to print CPU
> >
On Tue, Jan 29, 2013 at 10:55:24AM +0800, Xiao Guangrong wrote:
> On 01/29/2013 08:21 AM, Marcelo Tosatti wrote:
> > On Wed, Jan 23, 2013 at 06:05:29PM +0800, Xiao Guangrong wrote:
> >> In order to detecting spte remapping, we can simply check whether the
> >> spte has already been pointing to the
[ Reposting with a much shorter cc list as this patch didn't make it to
lkml.]
These are the simple ones.
File systems that use generic_file_aio_read() and generic_file_aio_write()
can trivially support generic_file_read_iter() and
generic_file_write_iter().
This patch adds those
Hi,
while analyzing the comedi drivers, I noticed that quite a lot of them use a
more or less similar find_boardinfo function.
e.g.:
cb_pcidas64.c
static const struct pcidas64_board
*cb_pcidas64_find_pci_board(struct pci_dev *pcidev)
{
unsigned int i;
for (i = 0; i <
On Wed, 2013-01-30 at 00:19 +0100, Rafael J. Wysocki wrote:
> On Tuesday, January 29, 2013 03:57:10 PM Toshi Kani wrote:
> > On Tue, 2013-01-29 at 22:32 +0100, Rafael J. Wysocki wrote:
> > > On Tuesday, January 29, 2013 07:50:43 AM Toshi Kani wrote:
> > > > On Tue, 2013-01-29 at 12:28 +0100,
On Thu, 24 Jan 2013, Joonsoo Kim wrote:
> From: Joonsoo Kim
>
> Now, there is no user for vmregion.
> So remove it.
>
> Signed-off-by: Joonsoo Kim
> Signed-off-by: Joonsoo Kim
Acked-by: Nicolas Pitre
>
> diff --git a/arch/arm/mm/Makefile b/arch/arm/mm/Makefile
> index 8a9c4cb..4e333fa
On Tue, 29 Jan 2013, Joonsoo Kim wrote:
> On Mon, Jan 28, 2013 at 01:04:24PM -0500, Nicolas Pitre wrote:
> > On Mon, 28 Jan 2013, Will Deacon wrote:
> >
> > > Hello,
> > >
> > > On Thu, Jan 24, 2013 at 01:28:51AM +, Joonsoo Kim wrote:
> > > > In current implementation, we used ARM-specific
On Mon, 2013-01-21 at 18:37 +0800, Zhenjiao Lu wrote:
> Dear Madam/Sir,
>
> Hello & Greetings from China.
>
> I am a college student in China, now working on the thesis paper,
> which is about the performance of Real Time Linux on embedded devices.
> And I am quite a freshmen in Linux.
>
> I
From: Stephen Warren
Within hibernate.c, hibernation_platform_enter() is only called from
power_down(), which in turn is only called by hibernate() after having
called hibernation_snapshot(), which in turn calls create_image() which
in turn calls disable_nonboot_cpus().
Elsewhere,
On Tuesday, January 29, 2013 03:57:10 PM Toshi Kani wrote:
> On Tue, 2013-01-29 at 22:32 +0100, Rafael J. Wysocki wrote:
> > On Tuesday, January 29, 2013 07:50:43 AM Toshi Kani wrote:
> > > On Tue, 2013-01-29 at 12:28 +0100, Rafael J. Wysocki wrote:
> > > > On Monday, January 28, 2013 07:35:39 PM
Hi,
On Tue, Jan 29, 2013 at 6:08 PM, Russell King - ARM Linux
wrote:
> On Tue, Jan 29, 2013 at 05:54:24PM +0200, Ruslan Bilovol wrote:
>> CPU implementer : 0x41
>> CPU name: OMAP4470 ES1.0 HS
>
> Sigh. No. Look at what you're doing - look carefully at the above.
>
> "CPU implementer" -
Hi,
On Tue, Jan 29, 2013 at 6:02 PM, Nishanth Menon wrote:
>
> On 17:54-20130129, Ruslan Bilovol wrote:
> > Hi,
> >
> > The following patches update cpuinfo to print CPU
> > model name for ARM. First patch exactly makes needed
> > changes for ARM architecture
On Fri, Jan 25, 2013 at 7:25 PM, Maxim V. Patlasov
wrote:
> The .writepages one is required to make each writeback request carry more than
> one page on it.
>
> Changed in v2:
> - fixed fuse_prepare_write() to avoid reads beyond EOF
> - fixed fuse_prepare_write() to zero uninitialized part of
On Tue, 29 Jan 2013 15:40:27 -0600
Seth Jennings wrote:
> This patch adds the documentation file for the zswap functionality
OK, that sort-of covers some of the things I asked about, although it
is rather skimpy.
It doesn't address pagefaults at all!
--
To unsubscribe from this list: send the
On Tue, 2013-01-29 at 22:32 +0100, Rafael J. Wysocki wrote:
> On Tuesday, January 29, 2013 07:50:43 AM Toshi Kani wrote:
> > On Tue, 2013-01-29 at 12:28 +0100, Rafael J. Wysocki wrote:
> > > On Monday, January 28, 2013 07:35:39 PM Toshi Kani wrote:
> > > > On Mon, 2013-01-28 at 13:59 +0100, Rafael
On Tue, 29 Jan 2013 15:40:26 -0600
Seth Jennings wrote:
> This patchset adds support for flush pages out of the compressed
> pool to the swap device
I do so hate that word "flush". Sometimes it means "writeback", other
times it means "invalidate". And perhaps it means "copy elsewhere then
On Thu, Jan 24, 2013 at 6:14 PM, Steven Rostedt wrote:
> I tried to get my snowball board working on the latest kernel, but it
> locks up hard very early on boot up.
>
> I bisected it down to this commit:
>
> commit ebc96db7632f987e0b9bffcb782cf5cfb8afb0dd
> Author: Ulf Hansson
> Date: Mon
On Fri, Jan 25, 2013 at 7:24 PM, Maxim V. Patlasov
wrote:
> Any write request requires a file handle to report to the userspace. Thus
> when we close a file (and free the fuse_file with this info) we have to
> flush all the outstanding writeback cache. Note, that simply calling the
>
On Fri, Jan 25, 2013 at 05:31:09PM -0800, Tejun Heo wrote:
> idr_destroy() can destroy idr by itself and idr_remove_all() is being
> deprecated. Drop reference to idr_remove_all(). Note that the code
> wasn't completely correct before because idr_remove() on all entries
> doesn't necessarily
On Tue, Jan 29, 2013 at 02:03:30PM +0300, Stanislav Kinsbursky wrote:
> There could be a service transport, which is processed by service thread and
> racing in the same time with per-net service shutdown like listed below:
>
> CPU#0:CPU#1:
>
> svc_recv
On Tuesday 29 January 2013, Linus Walleij wrote:
> > --- a/arch/arm/Kconfig
> > +++ b/arch/arm/Kconfig
> > @@ -1632,7 +1632,7 @@ config ARCH_NR_GPIO
> > default 355 if ARCH_U8500
> > default 264 if MACH_H4700
> > default 512 if SOC_OMAP5
> > - default 288 if
On Sat, Jan 26, 2013 at 02:50:43PM +0900, Kyungsik Lee wrote:
> This patchset is for supporting LZ4 compressed kernel and initial ramdisk on
> the x86 and ARM architectures.
Have you considered the 'high compression' mode of lz4?
http://code.google.com/p/lz4/source/browse/trunk/lz4hc.c
The
Le 29/01/2013 23:41, Linus Walleij a écrit :
> On Sun, Jan 27, 2013 at 8:02 PM, Maxime Ripard
> wrote:
>
>> Since the pin controller of sunxi chips is represented as a single bank
>> in the driver.
>> Since this is neither convenient nor represented that way in the
>> datasheets, define a custom
Hi Linus,
This is a late pinctrl fix pull request, we had to revert out the pinctrl-single
GPIO backend, because of, well, design issues. We're cooking a better
thing for the next cycle.
Please pull it in!
Yours,
Linus Walleij
The following changes since commit
On Tue, 29 Jan 2013 15:40:22 -0600
Seth Jennings wrote:
> This patch promotes the slab-based zsmalloc memory allocator
> from the staging tree to lib/
Hate to rain on the parade, but... we haven't reviewed zsmalloc
yet. At least, I haven't, and I haven't seen others do so.
So how's about we
On 01/29/2013 04:14 PM, Joe Perches wrote:
> On Tue, 2013-01-29 at 15:40 -0600, Seth Jennings wrote:
>> The code required for the flushing is in a separate patch now
>> as requested.
>
> What tree does this apply to?
> Both -next and linus fail to compile.
Link to build instruction in the cover
Dimitri and Robin have taken over GRU maintenance.
Linux on Altix is no longer maintained except as part of ia64, and
there's already a separate IA64 maintainer entry.
Signed-off-by: Bjorn Helgaas
---
MAINTAINERS | 11 ++-
1 file changed, 2 insertions(+), 9 deletions(-)
diff --git
Hi Linus,
Le 29/01/2013 23:38, Linus Walleij a écrit :
> On Mon, Jan 28, 2013 at 9:33 PM, Maxime Ripard
> wrote:
>
>> The IP responsible for the muxing on the Allwinner SoCs are also
>> handling the GPIOs on the system. This patch adds the needed driver that
>> relies on the pinctrl driver for
On Sun, Jan 27, 2013 at 8:02 PM, Maxime Ripard
wrote:
> Since the pin controller of sunxi chips is represented as a single bank
> in the driver.
> Since this is neither convenient nor represented that way in the
> datasheets, define a custom of_xlate function with the layout flag>
>
>
On Sat, Jan 26, 2013 at 3:36 PM, Maxime Ripard
wrote:
> The Allwinner A10 has 9 banks of 32 GPIOs available, so it doesn't fit
> in the usual 256 limit set by gpio.h. Increase this number to 288.
>
> Signed-off-by: Maxime Ripard
> ---
> arch/arm/Kconfig |2 +-
> 1 file changed, 1
On Mon, Jan 28, 2013 at 9:33 PM, Maxime Ripard
wrote:
> The IP responsible for the muxing on the Allwinner SoCs are also
> handling the GPIOs on the system. This patch adds the needed driver that
> relies on the pinctrl driver for most of its operations.
>
> The number of pins available for
On Tue, 2013-01-29 at 15:10 -0500, Vivek Goyal wrote:
> On Tue, Jan 29, 2013 at 03:01:13PM -0500, Mimi Zohar wrote:
>
> [..]
> > > Hi Mimi,
> > >
> > > Can we add another field to ima_rule_entry, say .enforcement to control
> > > the behavior of .action. Possible values of .enforcement could be,
On Tue, Jan 29, 2013 at 6:10 AM, Sachin Kamat wrote:
> Patch titled "pinctrl: exynos: change PINCTRL_EXYNOS option"
> (linux-next commit Id: 7452b64d) which is present in linux-next is
> missing in the mainline kernel.
Do I haven't sent my pull request for the pinctrl fixes yet.
> This patch
On Fri, Jan 25, 2013 at 7:24 PM, Maxim V. Patlasov
wrote:
> If writeback cache is on, buffered write doesn't result in immediate mtime
> update in userspace because the userspace will see modified data later, when
> writeback happens. Consequently, mtime provided by userspace may be older than
>
In some cases BIOS may not enable WC+ memory type on family 10
processors, instead converting what would be WC+ memory to CD type.
On guests using nested pages this could result in performance
degradation. This patch enables WC+.
Signed-off-by: Boris Ostrovsky
---
On Tue, 2013-01-29 at 15:40 -0600, Seth Jennings wrote:
> The code required for the flushing is in a separate patch now
> as requested.
What tree does this apply to?
Both -next and linus fail to compile.
There's a whitespace error applying 3/7 (line 543 in zswap.c)
and on 3.8-rc5 (allyesconfig
Resending since previous message went with incorrect From header. Also
fixing redundant check in the second patch.
Enable WC+ memory type on AMD family 10h processors if BIOS doesn't do
this. WC+ is used only in in virtualized scenarios and never in bare metal
cases (see AMD APM v2).
Also clean
Clean up multiple declarations of variable used for rd/wrmsr
Signed-off-by: Boris Ostrovsky
---
arch/x86/kernel/cpu/amd.c | 29 -
1 files changed, 12 insertions(+), 17 deletions(-)
diff --git a/arch/x86/kernel/cpu/amd.c b/arch/x86/kernel/cpu/amd.c
index
On Fri, Jan 25, 2013 at 3:14 PM, Arnd Bergmann wrote:
> nmk_prcm_gpiocr_get_mode is only needed for debugfs output at
> the moment, which can be compile-time disabled. Marking
> the function __maybe_unused still gives us compile-time
> coverage, but avoids a gcc warning.
>
> Without this patch,
On 01/10/2013 11:28 PM, Eric W. Biederman wrote:
...
> I don't have any problem with generic code in the reboot path
> doing:
> if (cpu_online(0))
> set_cpus_allowed_ptr(current, cpumask_of(0));
It looks like that API just affects the scheduler, and not whether the
other CPUs are actually
On Fri, Jan 25, 2013 at 3:14 PM, Arnd Bergmann wrote:
> Functions called from a driver probe() method must not be
> marked __init, because they may get called after the
> init phase is done, when the device shows up late, or
> because of deferred probing.
>
> Without this patch, building
On Tue, Jan 29, 2013 at 04:01:34PM +, Russell King - ARM Linux wrote:
> On Tue, Jan 29, 2013 at 10:34:53AM -0500, Alan Stern wrote:
> > On Mon, 28 Jan 2013, Russell King - ARM Linux wrote:
> >
> > > On Mon, Jan 28, 2013 at 10:17:33AM -0500, Alan Stern wrote:
> > > > On Mon, 28 Jan 2013, Roger
Hey, Kent.
On Tue, Jan 29, 2013 at 01:45:37PM -0800, Kent Overstreet wrote:
> It would definitely be cleaner if the global counter was also 32 bits (I
> probably should've done it that way at first) but it works with it being
> bigger _provided the sum of the percpu counters is sign extended_
> -Original Message-
> From: Shuah Khan [mailto:shuahk...@gmail.com]
> Sent: Tuesday, January 29, 2013 4:40 PM
> To: Deucher, Alexander
> Cc: Linus Torvalds; Linux Kernel Mailing List
> Subject: Re: Linux 3.8-rc4
>
> On Tue, Jan 29, 2013 at 1:13 PM, Deucher, Alexander
> wrote:
> >>
On 01/10/2013 10:59 PM, Eric W. Biederman wrote:
...
> disable_nonboot_cpus() should really be called
> sometimes_dangerously_hotunplug_all_but_one_cpu().
>
> If that code is going to be something other than power management
> specific it is not cool that disable_nonboot_cpus() is not always
>
On 01/29/2013 08:49 PM, Oleg Nesterov wrote:
> On 01/29, Jiri Slaby wrote:
>>
>> On 01/29/2013 08:07 PM, Oleg Nesterov wrote:
>>>
>>> Change set_termios/set_termiox to return -ERESTARTSYS to fix this
>>> particular problem.
>>
>> This looks reasonable. However given the link above says:
>> You
On Tue, Jan 29, 2013 at 12:49 AM, Ingo Molnar wrote:
>
> * Wang, Song-Bo (Stoney) wrote:
>
>> [...] Due to this mode mismatch, with specific HW
>> configurations, there will be intermittent lost interrupts,
>> which could result in a hang or data loss.
>
> That's the key piece of information
On Tue, 29 Jan 2013, xtu4 wrote:
> Subject: [PATCH] [SEQ_FILE] Avoid high order memory allocating with kmalloc
> when read large seq file
>
> currently, when dumpstate access /proc/xxx/binder , this binder include lots
> of info,
> it will use seq_read in kernel, in this function, it will
On Tue, Jan 29, 2013 at 12:02:18PM -0800, Tejun Heo wrote:
> Hello, Kent.
>
> On Tue, Jan 29, 2013 at 11:51:41AM -0800, Kent Overstreet wrote:
> > > What about overflow? Note that we can have systemetic cases where ref
> > > is gotten on one cpu and put on another transferring counts in a
> > >
On Tuesday, January 29, 2013 08:00:23 PM Viresh Kumar wrote:
> On 29 January 2013 17:21, Rafael J. Wysocki wrote:
> > On Tuesday, January 29, 2013 10:09:59 AM Viresh Kumar wrote:
> >> With the addition of following patch, related_cpus is required to be set by
> >> cpufreq platform drivers:
> >>
>
This patch promotes the slab-based zsmalloc memory allocator
from the staging tree to lib/
zswap depends on this allocator for storing compressed RAM pages
in an efficient way under system wide memory pressure where
high-order (greater than 0) page allocation are very likely to
fail.
For more
This patch adds the documentation file for the zswap functionality
Signed-off-by: Seth Jennings
---
Documentation/vm/zswap.txt | 73 ++
1 file changed, 73 insertions(+)
create mode 100644 Documentation/vm/zswap.txt
diff --git
debugfs currently lack the ability to create attributes
that set/get atomic_t values.
This patch adds support for this through a new
debugfs_create_atomic_t() function.
Signed-off-by: Seth Jennings
Acked-by: Greg Kroah-Hartman
---
fs/debugfs/file.c | 42
Sorry for the churn but just this set might be easier to review.
The code required for the flushing is in a separate patch now
as requested.
Changelog:
v4:
* Added Acks (Minchan)
* Separated flushing functionality into standalone patch
for easier review (Minchan)
* fix comment on zswap enabled
zswap is a thin compression backend for frontswap. It receives
pages from frontswap and attempts to store them in a compressed
memory pool, resulting in an effective partial memory reclaim and
dramatically reduced swap device I/O.
Additionally, in most cases, pages can be retrieved from this
This patchset adds support for flush pages out of the compressed
pool to the swap device
Signed-off-by: Seth Jennings
---
mm/zswap.c | 451 ++---
1 file changed, 434 insertions(+), 17 deletions(-)
diff --git a/mm/zswap.c b/mm/zswap.c
swap_writepage() is currently where frontswap hooks into the swap
write path to capture pages with the frontswap_store() function.
However, if a frontswap backend wants to "resume" the writeback of
a page to the swap device, it can't call swap_writepage() as
the page will simply reenter the
To prevent flooding the swap device with writebacks, frontswap
backends need to count and limit the number of outstanding
writebacks. The incrementing of the counter can be done before
the call to __swap_writepage(). However, the caller must receive
a notification when the writeback completes in
On Tuesday, January 29, 2013 08:09:08 PM Viresh Kumar wrote:
> Currently cpufreq_add_dev() firsts allocates policy, calls driver->init() and
> then checks if this cpu is already managed or not. And if it is already
> managed,
> free its policy.
>
> We can save all this if we somehow know cpu is
On Tue, Jan 29, 2013 at 1:13 PM, Deucher, Alexander
wrote:
>> -Original Message-
>> From: Shuah Khan [mailto:shuahk...@gmail.com]
>> Sent: Tuesday, January 29, 2013 2:11 PM
>> To: Deucher, Alexander
>> Cc: Linus Torvalds; Linux Kernel Mailing List
>> Subject: Re: Linux 3.8-rc4
>>
>> On
2013/1/29 Steven Rostedt :
> On Mon, 2013-01-28 at 21:36 -0500, Steven Rostedt wrote:
>
>> [root@bxtest ~]# time /work/c/kernelspin 10
>>
>> real 0m10.001s
>> user 0m1.114s
>> sys 0m8.886s
>>
>>
>> But after enabling the force context_tracking I get this:
>>
>> [root@bxtest ~]# time
On Tue, Jan 29, 2013 at 10:23:09PM +0100, Sebastian Hesselbarth wrote:
> This patch cleans unneccessary includes and reorders the remaining
> includes in common dove code.
>
> Signed-off-by: Sebastian Hesselbarth
> ---
> Changelog:
> [v2]
> - restructure patches to first cleanup common.c
On Tue, Jan 29, 2013 at 1:28 PM, Borislav Petkov wrote:
> Hi,
>
> this is rc5 + tip/master from 2 days ago, when resuming I get this fun
> message:
>
> ...
> [15117.684975] Restarting tasks ... done.
> [15117.687201] video LNXVIDEO:00: Restoring backlight state
> [15117.720469] ehci-pci
From: Boris Ostrovsky
In some cases BIOS may not enable WC+ memory type on family 10
processors, instead converting what would be WC+ memory to CD type.
On guests using nested pages this could result in performance
degradation. This patch enables WC+.
Signed-off-by: Boris Ostrovsky
---
On 01/28/2013 08:57 PM, John L. Males wrote:
> I was not suggesting you are responsible for the bug at all. On
Okay then :)
> I have no custom patches to the kernel.
okay.
> I looked at the RedHat bug 468794. The bug seems to indicate it
> was never fixed. The bug was reported against
>
From: Boris Ostrovsky
Clean up multiple declarations of variable used for rd/wrmsr
Signed-off-by: Boris Ostrovsky
---
arch/x86/kernel/cpu/amd.c | 29 -
1 files changed, 12 insertions(+), 17 deletions(-)
diff --git a/arch/x86/kernel/cpu/amd.c
From: Boris Ostrovsky
Enable WC+ memory type on AMD family 10h processors if BIOS doesn't do
this. WC+ is used only in in virtualized scenarios and never in bare metal
cases (see AMD APM v2).
Also clean up init_amd() a little.
Boris Ostrovsky (2):
AMD,x86: Clean up init_amd()
x86,AMD:
On Tue, Jan 29, 2013 at 12:49 AM, Ingo Molnar wrote:
>
> * Wang, Song-Bo (Stoney) wrote:
>
>> [...] Due to this mode mismatch, with specific HW
>> configurations, there will be intermittent lost interrupts,
>> which could result in a hang or data loss.
Wang,
Maybe off topic, You should never
On Tue, Jan 29, 2013 at 10:23:10PM +0100, Sebastian Hesselbarth wrote:
> In the beginning of DT for Dove it was reasonable to have it close to
> non-DT code. With improved DT support, it became more and more difficult
> to not break non-DT while changing DT code.
>
> This patch splits up DT board
On Mon, 2013-01-28 at 21:36 -0500, Steven Rostedt wrote:
> [root@bxtest ~]# time /work/c/kernelspin 10
>
> real 0m10.001s
> user 0m1.114s
> sys 0m8.886s
>
>
> But after enabling the force context_tracking I get this:
>
> [root@bxtest ~]# time /work/c/kernelspin 10
>
> real 0m10.001s
>
On Tuesday, January 29, 2013 07:50:43 AM Toshi Kani wrote:
> On Tue, 2013-01-29 at 12:28 +0100, Rafael J. Wysocki wrote:
> > On Monday, January 28, 2013 07:35:39 PM Toshi Kani wrote:
> > > On Mon, 2013-01-28 at 13:59 +0100, Rafael J. Wysocki wrote:
> > > > From: Rafael J. Wysocki
> > > >
> > > >
> Andrew Morton wrote:
>
>On Sat, 26 Jan 2013 14:50:43 +0900
>Kyungsik Lee wrote:
>> This patchset is for supporting LZ4 compressed kernel and initial ramdisk on
>> the x86 and ARM architectures.
>>
>> According to [[http://code.google.com/p/lz4/,]] LZ4 is a very fast lossless
>> compression
Hello Huang,
Le mardi 22 janvier 2013 02:30:30, Huang Shijie a écrit :
> In nand_wait(), the timeo for panic_nand_wait() is assigned with
> wrong value(jiffies + some delay). The timeo should be set like the
> panic_nand_write() does.
>
> This patch fixes it, and also uses the msecs_to_jiffies()
Em Tue, Jan 29, 2013 at 12:48:51PM +0100, Stephane Eranian escreveu:
> Arnaldo,
>
> V7 posted. It's a rebase done against your perf/core, was no big deal.
> Let me know if it works for you now.
Thanks, it is now merged in my perf/core branch,
- Arnaldo
>
> On Tue, Jan 29, 2013 at 2:41 AM,
Am 29.01.2013 21:35, schrieb Alexander Holler:
So, if the above down_timeout_killable() is only down_interruptible(),
as in kernel 3.7.5, the box would not shutdown afterwards, because on
shutdown no signal would be send to that kernel-thread which called
dlfb_free_urb_list().
A last note:
PCI defines display class VGA regions at I/O port address 0x3b0, 0x3c0
and MMIO address 0xa. As these are non-overlapping, we can ignore
the I/O port vs MMIO difference and expose them both in a single
region. We make use of the VGA arbiter around each access to
configure chipset access as
Hi James,
On Tue, 29 Jan 2013 14:30:52 + James Hogan wrote:
>
> Please can you add the following branch to linux-next for Meta
> architecture support:
>
> git://github.com/jahogan/metag-linux.git for-next
Added from today (though there may not be a linux-next release today).
Thanks for
Hi Vineet,
On Wed, 30 Jan 2013 07:44:52 +1100 Stephen Rothwell
wrote:
>
> On Mon, 28 Jan 2013 12:40:24 +0530 Vineet Gupta
> wrote:
> >
> > Stephen, can you please add the following branch (rebased off 3.8-rc5) to
> > linux-next
> >
> >
On Tue, Jan 29, 2013 at 12:35:00PM -0800, Tejun Heo wrote:
> Generally looks good to me although I haven't really delved into the
> behavior (you're gonna be there for the fallouts, right?). Just some
> minor comments.
yes, I'll.
> > +static int propagate_behavior(struct dev_cgroup *devcg_root)
On 01/29/2013 02:35 PM, Konrad Rzeszutek Wilk wrote:
> On Mon, Jan 28, 2013 at 03:49:22PM -0600, Seth Jennings wrote:
>> debugfs currently lack the ability to create attributes
>> that set/get atomic_t values.
>>
>> This patch adds support for this through a new
>> debugfs_create_atomic_t()
From: Jason Wang
Date: Mon, 28 Jan 2013 19:05:16 +0800
> This is an update version of last version to fix the handling of polling
> errors
> in vhost/vhost_net.
>
> Currently, vhost and vhost_net ignore polling errors which can lead kernel
> crashing when it tries to remove itself from
201 - 300 of 1454 matches
Mail list logo
