From: Dongsheng Yang
When we synthesize the threads, we are looking for the infomation under
/proc. But it is only for host.
This patch look for the path of proc under machine->root_dir, then
XXX__synthesize_threads() functions can support guest machines.
Signed-off-by: Dongsheng Yang
Cc:
From: Arnaldo Carvalho de Melo
Hi Ingo,
This one has the 34 out of 35 patches from the previous pull req,
removing
the 'perf stat' one about not printing stats for workloads we failed to start,
that
requires more thinking and introduced a regression.
I'm suppressing those
From: Dongsheng Yang
As the default guest is designed to handle orphan kernel symboles with
--guestkallsysms and --guestmodules, it has no user space.
So we should skip synthesizing threads if machine is default guest.
Signed-off-by: Dongsheng Yang
Cc: David Ahern
Cc: Ingo Molnar
Cc: Jiri
On Fri, 2013-12-27 at 21:12 +0100, Julia Lawall wrote:
> On Fri, 27 Dec 2013, Joe Perches wrote:
>
> > On Fri, 2013-12-27 at 07:48 -0800, Eric Dumazet wrote:
> > > On Fri, 2013-12-27 at 14:49 +0800, Ding Tianhong wrote:
> > > > Use possibly more efficient ether_addr_equal
> > > > to instead of
0) mei_me_hw_ready_wait() currently reads:
int err;
[...]
err = wait_event_interruptible_timeout(dev->wait_hw_ready,
dev->recvd_hw_ready,
mei_secs_to_jiffies(MEI_INTEROP_TIMEOUT));
[...]
if (!err &&
On Fri, 27 Dec 2013, Alessandro Zummo wrote:
> On Wed, 25 Dec 2013 20:32:12 +0100 (CET)
> Julia Lawall wrote:
>
>
> > Is it intentional that the error code returned by
> > hpet_register_irq_handler is put ina local variable that will not be seen
> > at label cleanup1? The return value is
On Fri, 27 Dec 2013, Joe Perches wrote:
> On Fri, 2013-12-27 at 07:48 -0800, Eric Dumazet wrote:
> > On Fri, 2013-12-27 at 14:49 +0800, Ding Tianhong wrote:
> > > Use possibly more efficient ether_addr_equal
> > > to instead of memcmp.
> []
> > > diff --git a/drivers/net/plip/plip.c
Em Fri, Dec 20, 2013 at 04:08:35PM -0300, Arnaldo Carvalho de Melo escreveu:
> User visible changes:
>
> Improvements:
>
> . Do not show stats if workload fails in 'stat' (David Ahern)
Hi Ingo,
Please hold on, as reported elsewhere, the above change broke
'perf stat valid-workload', so
On Mon, 23 Dec 2013, Sebastian Andrzej Siewior wrote:
> Dear RT folks!
>
> I'm pleased to announce the v3.12.6-rt9 patch set.
>
> Changes since v3.12.6-rt8
> - A patch from Thomas Gleixner not to raise the timer softirq
> unconditionally (only if a timer is pending)
>
This one seems to
Seems like DH87RL was working with 3.2.0-55-generic-pae unfortunately
we don't have such a board for testing and customer patience is
limited to bisect the kernel.
Does anyone have a clue what modification could have killed USB 3.0
support within those releases?
It does not seem to be SG support.
On Fri, Dec 27, 2013 at 7:16 PM, Tony Lindgren wrote:
> * Belisko Marek [131221 15:58]:
>> OK seems I found solution:
>> http://marc.info/?l=linux-omap=138756097116464=2
>
> Good to hear :)
>
>> @Tony: Is this going to 3.13?
>
> Sorry too intrusive for 3.13, should be all set to go into v3.14.
On (27/12/13 20:44), Heinz Diehl put forth the
proposition:
On 27.12.2013, David Woodfall wrote:
But any of the newer kernel versions I've tested only give me
performance and powersave.
I don't use any Fedora kernel, so I can't tell which governors are
enabled in those. You should check
On 27.12.2013, David Woodfall wrote:
> But any of the newer kernel versions I've tested only give me
> performance and powersave.
I don't use any Fedora kernel, so I can't tell which governors are
enabled in those. You should check the value of "CONFIG_CPU_FREQ_GOV"
in the respective .config
Hi!
> > Well, this one will be really smaller. And yes, it will make some
> > memory non-swappable, but I believe with triggers and infrastructure
> > for N900 (and similar) it will be worth it.
>
> Ah yes thats such a major proportion of platforms
I don't know other cellphone hardware in
Hello.
This is just an initial/preliminary heads-up, maybe mis-directed, about
a possible issue.
I upgraded 2 machines today to 3.10.25, and both shows some.. strangeness
within linux guests, which are also running 3.10.25. Revering to 3.10.24
in guests (compiled by the same compiler with the
Em Fri, Dec 27, 2013 at 02:49:02PM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Fri, Dec 27, 2013 at 09:20:11AM -0500, David Ahern escreveu:
> > On 12/27/13, 1:14 AM, Masami Hiramatsu wrote:
> > >Nowhere, since there is no terminal code for user
> > >command interface.
>
> > >Those memories are
Em Fri, Dec 27, 2013 at 06:03:27PM -0500, Dongsheng Yang escreveu:
> As what the usage showing, we can input a event_glob as an argument to list
> all symbols. But it does not work well right now.
>
> Example:
> # perf list kvmmmu
>
> List of pre-defined events (to be used in -e):
>
On Fri, 2013-12-27 at 20:10 +0100, Ben Hutchings wrote:
> On Fri, 2013-12-27 at 10:47 -0800, Greg Kroah-Hartman wrote:
> > On Fri, Dec 27, 2013 at 06:18:18PM +0100, Ben Hutchings wrote:
> > > snprintf() returns the number of bytes that could have been written
> > > (excluding the null), not the
Ich suche eine Partnerschaft bei der Beschaffung von 50Millionen US-Dollar
hinter sich gelassen um einen bestimmten verstorbenen Kunden (Anthony).Kontakt
per E-mail unten f?r mehr Details; philip.thomps...@yahoo.co.uk
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
On Fri, 2013-12-27 at 10:47 -0800, Greg Kroah-Hartman wrote:
> On Fri, Dec 27, 2013 at 06:18:18PM +0100, Ben Hutchings wrote:
> > snprintf() returns the number of bytes that could have been written
> > (excluding the null), not the actual number of bytes written. Given a
> > long enough subsystem
Hayes Wang :
[...]
> diff --git a/drivers/net/usb/cdc_ether.c b/drivers/net/usb/cdc_ether.c
> index 4b1c0f3..3e09887 100644
> --- a/drivers/net/usb/cdc_ether.c
> +++ b/drivers/net/usb/cdc_ether.c
> @@ -486,6 +486,7 @@ static const struct driver_info wwan_info = {
> #define ZTE_VENDOR_ID
I recently upgraded from 3.9.0 to 3.10.17 and found that I don't have
the same cpufreq governors available. I also tested with 3.12.6 and
3.13.0_rc5 with the same results.
3.9.0 tells me:
cat /sys/devices/system/cpu/*/cpufreq/scaling_available_governors
conservative ondemand powersave userspace
Hayes Wang :
[...]
> diff --git a/drivers/net/usb/r8152.c b/drivers/net/usb/r8152.c
> index b8bc3eb..a8ea848 100644
> --- a/drivers/net/usb/r8152.c
> +++ b/drivers/net/usb/r8152.c
[...]
> @@ -274,6 +274,9 @@ enum rtl_register_content {
> #define RTL8152_MAX_TX 10
> #define
On Fri, Dec 27, 2013 at 06:18:18PM +0100, Ben Hutchings wrote:
> snprintf() returns the number of bytes that could have been written
> (excluding the null), not the actual number of bytes written. Given a
> long enough subsystem or device name, these functions will advance
> beyond the end of the
On Fri, Dec 27, 2013 at 10:23:10AM -0800, Stephen Boyd wrote:
> On 12/27/13 10:10, Felipe Balbi wrote:
> > Hi,
> >
> > On Tue, Nov 12, 2013 at 04:51:36PM +0200, Ivan T. Ivanov wrote:
> >> From: "Ivan T. Ivanov"
> >>
> >> This patch fix compilation error when driver is compiled
> >> in
On Fri, Dec 27, 2013 at 03:47:31PM +0530, Tushar Behera wrote:
> On 27 December 2013 12:08, Greg KH wrote:
> > On Fri, Dec 27, 2013 at 12:00:20PM +0530, Tushar Behera wrote:
> >> On 27 December 2013 10:48, Greg KH wrote:
> >> > On Fri, Dec 27, 2013 at 10:37:28AM +0530, Tushar Behera wrote:
>
>
On Fri, Dec 27, 2013 at 7:13 PM, One Thousand Gnomes
wrote:
>> Plus, it will actually save CPU cycles, and thus significant power.
>
> All of which will be totally wiped out if you bump all the millions of
> x86 server boxes in the world up by one page of kernel space and cause a
> few disk I/Os
On Fri, Dec 27, 2013 at 08:54:10AM -0800, Andrey Smirnov wrote:
> Sorry for the spam, sent the first version of the reply in non plain/text.
>
> >> +static ssize_t ims_pcu_ofn_reg_data_show(struct device *dev,
> >> + struct device_attribute *dattr,
> >> +
On 12/27/13 10:10, Felipe Balbi wrote:
> Hi,
>
> On Tue, Nov 12, 2013 at 04:51:36PM +0200, Ivan T. Ivanov wrote:
>> From: "Ivan T. Ivanov"
>>
>> This patch fix compilation error when driver is compiled
>> in multi-platform builds.
>>
>> drivers/built-in.o: In function `msm_otg_link_clk_reset':
>>
* Belisko Marek [131221 15:58]:
> OK seems I found solution:
> http://marc.info/?l=linux-omap=138756097116464=2
Good to hear :)
> @Tony: Is this going to 3.13?
Sorry too intrusive for 3.13, should be all set to go into v3.14.
Regards,
Tony
--
To unsubscribe from this list: send the line
> Well, this one will be really smaller. And yes, it will make some
> memory non-swappable, but I believe with triggers and infrastructure
> for N900 (and similar) it will be worth it.
Ah yes thats such a major proportion of platforms
> Plus, it will actually save CPU cycles, and thus
Hi,
On Tue, Nov 12, 2013 at 04:51:36PM +0200, Ivan T. Ivanov wrote:
> From: "Ivan T. Ivanov"
>
> This patch fix compilation error when driver is compiled
> in multi-platform builds.
>
> drivers/built-in.o: In function `msm_otg_link_clk_reset':
> ./drivers/usb/phy/phy-msm-usb.c:314: undefined
On Fri, Dec 27, 2013 at 06:15:07PM +0100, Jochen Striepe wrote:
> Hi,
>
> On Sun, Dec 22, 2013 at 03:25:23AM +0100, Jochen Striepe wrote:
> > Applies, compiles, and runs smoothly on top of 3.12.6. I'll send word
> > if anything odd shows up.
>
> Tested with various loads, everything nice
Em Fri, Dec 27, 2013 at 09:20:11AM -0500, David Ahern escreveu:
> On 12/27/13, 1:14 AM, Masami Hiramatsu wrote:
> >Nowhere, since there is no terminal code for user
> >command interface.
> >Those memories are released when the program terminated.
> >I think it is just a waste of the time to free
You are QATAR Foundation beneficiary of $2 Million US Dollars this season. To
claim contact Mr. Tony Burt via email: innfros...@blumail.org within 24hrs
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo
From: Levente Kurusa
Date: Thu, 19 Dec 2013 16:03:16 +0100
> This is required so that we give up the last reference to the device.
> The kfree() has been removed because put_device will set the underlying kref's
> reference count to zero and hence vio_dev_release will get called resulting in
>
From: Levente Kurusa
Date: Thu, 19 Dec 2013 16:03:31 +0100
> This is required so that we give up the last reference to the device.
>
> Signed-off-by: Levente Kurusa
...
> @@ -2377,8 +2377,10 @@ static int afiucv_iucv_init(void)
> af_iucv_dev->release = (void (*)(struct device *))kfree;
From: Levente Kurusa
Date: Thu, 19 Dec 2013 16:03:30 +0100
> This is required so that we give up the last reference to the device.
>
> Signed-off-by: Levente Kurusa
...
> @@ -154,8 +154,10 @@ int atm_register_sysfs(struct atm_dev *adev, struct
> device *parent)
>
> dev_set_name(cdev,
From: Sasha Levin
Date: Wed, 18 Dec 2013 23:49:42 -0500
> Binding might result in a NULL device, which is dereferenced
> causing this BUG:
...
> Signed-off-by: Sasha Levin
Applied and queued up for -stable, thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
Hi,
On Sun, Dec 22, 2013 at 03:25:23AM +0100, Jochen Striepe wrote:
> Applies, compiles, and runs smoothly on top of 3.12.6. I'll send word
> if anything odd shows up.
Tested with various loads, everything nice and working so far.
Have a nice weekend,
Jochen.
--
To unsubscribe from this
On Wed, 25 Dec 2013 20:32:12 +0100 (CET)
Julia Lawall wrote:
> Is it intentional that the error code returned by
> hpet_register_irq_handler is put ina local variable that will not be seen
> at label cleanup1? The return value is retval, which is 0 at this point.
Well, I'd say it's an
From: Hayes Wang
Date: Fri, 27 Dec 2013 10:34:08 +0800
>
> +static int rtl_ops_init(struct r8152 *tp, const struct usb_device_id *id)
...
>
> + if (rtl_ops_init(tp, id)) {
> + netif_err(tp, probe, netdev, "Unknown Device");
> + return -ENODEV;
You're completely
Both x32 and x86-64 use the same struct rusage and struct rlimit for
system calls. But x32 log is 32-bit. This patch change uapi
to use __kernel_long_t in struct rusage and
__kernel_ulong_t in and struct rlimit if __BITS_PER_LONG == 64.
Signed-off-by: H.J. Lu
---
X32 IPC system call is the same as x86-64 IPC system call, which uses
64-bit integer for unsigned long in struct ipc64_perm. But x32 long is
32 bit. This patch replaces unsigned long in uapi struct ipc64_perm with
__kernel_ulong_t if __BITS_PER_LONG == 64.
Signed-off-by: H.J. Lu
---
Both x32 and x86-64 use the same struct mq_attr for system calls. But
x32 long is 32-bit. This patch replaces long with __kernel_long_t in
struct mq_attr if __BITS_PER_LONG == 64.
Signed-off-by: H.J. Lu
---
include/uapi/linux/mqueue.h | 18 +-
1 file changed, 13 insertions(+),
Both x32 and x86-64 use the same struct semid64_ds for system calls.
But x32 long is 32-bit. This patch replaces unsigned long with
__kernel_ulong_t in x86 struct semid64_ds.
Signed-off-by: H.J. Lu
---
arch/x86/include/uapi/asm/sembuf.h | 10 +-
1 file changed, 5 insertions(+), 5
Both x32 and x86-64 use the same struct msqid64_ds for system calls.
But x32 long is 32-bit. This patch replaces unsigned long with
__kernel_ulong_t in struct msqid64_ds if __BITS_PER_LONG == 64.
Signed-off-by: H.J. Lu
---
include/uapi/asm-generic/msgbuf.h | 19 ++-
1 file
Both x32 and x86-64 use the same struct shmid64_ds/shminfo64/shm_info for
system calls. But x32 long is 32-bit. This patch replaces unsigned long
with __kernel_ulong_t in struct shmid64_ds/shminfo64/shm_info if
__BITS_PER_LONG == 64.
Signed-off-by: H.J. Lu
---
include/uapi/asm-generic/shmbuf.h
X32 msgsnd/msgrcv system calls are the same as x86-64 msgsnd/msgrcv system
calls, which use 64-bit integer for long in struct msgbuf . But x32 long
is 32 bit. This patch replaces long in struct msgbuf with __kernel_long_t
if __BITS_PER_LONG == 64.
Signed-off-by: H.J. Lu
---
X32 uses the same kernel system call interface as x86-64 for many
system calls. However, "long" is 64-bit for x86-64 and is 32-bit for
x32. Where long or unsigned long are used in struct types for such
system calls, they are wrong for x32. __kernel_[u]long_t is [unsigned]
long for all ABIs
X32 adjtimex system call is the same as x86-64 adjtimex system call,
which uses 64-bit integer for long in struct timex. But x32 long is
32 bit. This patch replaces long in struct timex with __kernel_long_t
if __BITS_PER_LONG == 64.
Signed-off-by: H.J. Lu
---
include/uapi/linux/timex.h | 46
On 12/27/2013 06:01 PM, Gleb Natapov wrote:
> On Fri, Dec 27, 2013 at 06:52:48PM +0200, Gleb Natapov wrote:
>> On Fri, Dec 27, 2013 at 03:15:39PM +0100, Kashyap Chamarthy wrote:
>>> [. . .]
>>>
> KVM does not emulate P-states at all. intel_pstate_init() calls
>
On Fri, Dec 27, 2013 at 07:01:48PM +0200, Gleb Natapov wrote:
> On Fri, Dec 27, 2013 at 06:52:48PM +0200, Gleb Natapov wrote:
> > On Fri, Dec 27, 2013 at 03:15:39PM +0100, Kashyap Chamarthy wrote:
> > > [. . .]
> > >
> > > >> KVM does not emulate P-states at all. intel_pstate_init() calls
> > >
snprintf() returns the number of bytes that could have been written
(excluding the null), not the actual number of bytes written. Given a
long enough subsystem or device name, these functions will advance
beyond the end of the on-stack buffer in dev_vprintk_exit(), resulting
in an information
I just got another USB 3.0 bugreport, the entire system crashed. That
particular customer already filed a bugreport in November 2013 that
his system is in a bad state when using some USB 2.0 media devices
which even have opensource drivers built into the kernel.
USB 3.0 support with Linux seems
New function reiserfs_tmpfile:
-Duplicate reiserfs_create
-Remove dquot_initialize (cf ext2/tmpfile)
-Remove add_entry code
-Add d_tmpfile generic call
-Add add_save_link (cf ext3/orphan_add)
reiserfs_link function:
-Add remove_save_link (cf ext3/orphan_del)
Saved link is removed in normal
On Fri, 2013-12-27 at 07:48 -0800, Eric Dumazet wrote:
> On Fri, 2013-12-27 at 14:49 +0800, Ding Tianhong wrote:
> > Use possibly more efficient ether_addr_equal
> > to instead of memcmp.
[]
> > diff --git a/drivers/net/plip/plip.c b/drivers/net/plip/plip.c
[]
> > @@ -549,7 +549,7 @@ static __be16
On Fri, Dec 27, 2013 at 06:52:48PM +0200, Gleb Natapov wrote:
> On Fri, Dec 27, 2013 at 03:15:39PM +0100, Kashyap Chamarthy wrote:
> > [. . .]
> >
> > >> KVM does not emulate P-states at all. intel_pstate_init() calls
> > >> intel_pstate_msrs_not_valid() before printing "Intel P-state driver
> >
Sorry for the spam, sent the first version of the reply in non plain/text.
>> +static ssize_t ims_pcu_ofn_reg_data_show(struct device *dev,
>> + struct device_attribute *dattr,
>> + char *buf)
>> +{
>> + struct
On Fri, Dec 27, 2013 at 03:15:39PM +0100, Kashyap Chamarthy wrote:
> [. . .]
>
> >> KVM does not emulate P-states at all. intel_pstate_init() calls
> >> intel_pstate_msrs_not_valid() before printing "Intel P-state driver
> >> initializing." which suppose to fail since it checks that two reads of
On Fri, 2013-12-27 at 15:54 +0100, Jean-Jacques Hiblot wrote:
> Hi Tom, Steven,
>
> I'm currently doing some tests with the event triggers
> (git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
> for-next).
> At the moment I can't use event triggers with probes dynamically
>
cc-ing doc. maintainer.
On 12/26/13 18:44, Fabian Frederick wrote:
> Add the following documentation-files with description :
> -autofs4-mount-control.txt
> -btrfs.txt
> -debugfs.txt
> -devpts.txt
> -fiemap.txt
> -gfs2-glocks.txt
> -gfs2-uevents.txt
> -omfs.txt
> -path-lookup.txt
>
On 27.12.2013 11:48, Pavel Machek wrote:
On Thu 2013-12-26 01:12:39, Ivaylo Dimitrov wrote:
From: Ivaylo Dimitrov
On memory limited devices, CMA fails easily when asked to allocate big
chunks of memory like framebuffer memory needed for video playback.
Add boot parameter "omapfb_memsize"
On 12/24, Suresh Thiagarajan wrote:
>
> Below is a small pseudo code on protecting/serializing the flag for global
> access.
> struct temp
> {
> ...
> spinlock_t lock;
> unsigned long lock_flags;
> };
> void my_lock(struct temp *t)
> {
>unsigned long flag; //
On 12/25/2013 03:22 AM, rui wang wrote:
>
> Yes that comment was what triggered me to think that the issue wasn't
> understood. You now have a clear enough explanation.
>
Rui, you've pointed out that my patch description in insufficient. I'll rewrite
it and resubmit with a much more detailed
On 12/24/2013 09:40 PM, Chen, Gong wrote:
> On Tue, Dec 24, 2013 at 08:19:09AM -0500, Prarit Bhargava wrote:
>> On 12/23/2013 09:51 PM, Chen, Gong wrote:
>>> On Mon, Dec 23, 2013 at 09:39:12AM -0500, Prarit Bhargava wrote:
diff --git a/arch/x86/kernel/irq.c b/arch/x86/kernel/irq.c
Introduce ff-memless-next module as a possible future replacement for
ff-memless.
Tested-by: Elias Vanderstuyft
Signed-off-by: Michal Malý
---
Documentation/input/ff-memless-next.txt | 149 ++
drivers/input/Kconfig | 12 +
drivers/input/Makefile | 2 +
From: Ivaylo Dimitrov
Use upstream hashtable implementation instead of generic code
Signed-off-by: Ivaylo Dimitrov
---
drivers/staging/tidspbridge/gen/gh.c | 141 +++-
drivers/staging/tidspbridge/include/dspbridge/gh.h |6 +-
On Fri, 2013-12-27 at 14:49 +0800, Ding Tianhong wrote:
> Use possibly more efficient ether_addr_equal
> to instead of memcmp.
>
> Cc: "David S. Miller"
> Signed-off-by: Ding Tianhong
> ---
> drivers/net/plip/plip.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git
On Fri 2013-12-27 14:18:26, One Thousand Gnomes wrote:
> > At least nokia N900 actually has "hardware acceleration" for LED
> > blinking. (Tiny CPU connected over i2c, able to control 3 LEDs, turing
> > complete with something like 20 _bits_ of storage and 30 program
> > steps). Apparently, it
On Fri, Dec 27, 2013 at 01:03:32PM +, Caizhiyong wrote:
> From: Cai Zhiyong
> Date: Fri, 27 Dec 2013 20:23:09 +0800
> Subject: [PATCH] mtd: nand: remove NAND_MAX_OOBSIZE and NAND_MAX_PAGESIZE
>
> remove NAND_MAX_OOBSIZE and NAND_MAX_PAGESIZE, dynamic allocate
> NAND buffer after detecting
Hi Tom, Steven,
I'm currently doing some tests with the event triggers
(git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
for-next).
At the moment I can't use event triggers with probes dynamically
created (with perf probe or via
/sys/kernel/debug/tracing/kprobe_events)
Hello.
On 27-12-2013 10:48, Ding Tianhong wrote:
Use the possibly more efficient ether_addr_equal or
ether_addr_equal_unaligned to instead of memcmp.
Cc: Ariel Elior
Signed-off-by: Ding Tianhong
---
drivers/net/ethernet/broadcom/bnx2x/bnx2x_sp.c| 10 --
Add Frederic, I am not sure I understand this correctly.
On 12/25, Rob Landley wrote:
>
> There are two values here, the first is seconds since boot time (which
> is just elapsed time; at one point it was ajusted for suspend and that
> was revered as confusing).
Hmm, uptime_proc_show() still
ghes_proc() always return 0 even failed to read estatus, so when it is
called in interrupt handler ghes_irq_func(), we don't know the interrupt
was handled well or not, because the ghes_irq_func() will return only
IRQ_HANDLED.
Signed-off-by: Ethan Zhao
---
drivers/acpi/apei/ghes.c | 4 ++--
1
Probably the qemu command line is more interesting, which is in this
comment and reproduced below.
https://bugzilla.redhat.com/show_bug.cgi?id=1046317#c1
/usr/bin/qemu-kvm \
-global virtio-blk-pci.scsi=off \
-nodefconfig \
-enable-fips \
-nodefaults \
-display none \
On Tuesday, December 24, 2013 09:36:01 PM Viresh Kumar wrote:
> Adding Dirk..
>
> On 24 December 2013 20:06, Josh Boyer wrote:
> > Hi All,
> >
> > We've had a report [1] that the pstate driver causes KVM guests to
> > fail to boot because of a divide error. See the backtrace below.
> >
> >
On 12/27/13, 1:14 AM, Masami Hiramatsu wrote:
Nowhere, since there is no terminal code for user
command interface.
Those memories are released when the program terminated.
I think it is just a waste of the time to free the memory
pieces which are not used(and allocated) repeatedly.
Or, is there
> At least nokia N900 actually has "hardware acceleration" for LED
> blinking. (Tiny CPU connected over i2c, able to control 3 LEDs, turing
> complete with something like 20 _bits_ of storage and 30 program
> steps). Apparently, it makes more stable patterns (timing is very hard
> to guarantee
[. . .]
>> KVM does not emulate P-states at all. intel_pstate_init() calls
>> intel_pstate_msrs_not_valid() before printing "Intel P-state driver
>> initializing." which suppose to fail since it checks that two reads of
>> MSR_IA32_APERF return different values, but KVM does not emulate this msr
On Thursday 26 December 2013 11:14 PM, Santosh Shilimkar wrote:
> Sricharan,
>
> On Wednesday 25 December 2013 11:52 PM, Sricharan R wrote:
>> Hi Thomas,
>> On Wednesday 18 December 2013 02:49 PM, Sricharan R wrote:
>>> Hi Thomas,
>>>
>>> On Tuesday 03 December 2013 03:57 PM, Sricharan R wrote:
On Fri, Dec 27, 2013 at 7:47 AM, Gleb Natapov wrote:
> On Fri, Dec 27, 2013 at 12:24:22PM +, One Thousand Gnomes wrote:
>> On Tue, 24 Dec 2013 21:36:01 +0530
>> Viresh Kumar wrote:
>>
>> > Adding Dirk..
>> >
>> > On 24 December 2013 20:06, Josh Boyer wrote:
>> > > Hi All,
>> > >
>> > >
Thomas,
> -Original Message-
> From: Neil Zhang
> Sent: 2013年12月13日 13:36
> To: Neil Zhang; t...@linutronix.de; haojian.zhu...@gmail.com;
> linux-kernel@vger.kernel.org
> Subject: RE: [PATCH v3] irqchip: mmp: avoid use head file in a specific arch
>
> Thomas,
>
> > -Original
On Fri 2013-12-27 06:39:55, Rob Landley wrote:
> On 12/26/13 10:58, Joe Xue wrote:
> >Hi all,
> >
> >I think Pavel's suggestion is a good idea, I'm starting to write another
> >trigger named Morse code trigger.
>
> Those who don't know history are doomed to fail the class and have
> to retake it
From: Cai Zhiyong
Date: Fri, 27 Dec 2013 20:23:09 +0800
Subject: [PATCH] mtd: nand: remove NAND_MAX_OOBSIZE and NAND_MAX_PAGESIZE
remove NAND_MAX_OOBSIZE and NAND_MAX_PAGESIZE, dynamic allocate
NAND buffer after detecting NAND writesize and oobsize.
- save memory. when use MACRO allocate
From: Cai Zhiyong
Date: Fri, 27 Dec 2013 20:23:09 +0800
Subject: [PATCH] mtd: nand: remove NAND_MAX_OOBSIZE and NAND_MAX_PAGESIZE
remove NAND_MAX_OOBSIZE and NAND_MAX_PAGESIZE, dynamic allocate
NAND buffer after detecting NAND writesize and oobsize.
- save memory. when use MACRO allocate
Hi!
> > Yes, Morse code can indicate any means. But when we look at the LEDs, would
> > we like to also have a Morse code book in hand?
> >
> > The burst led blink idea is because it is easy to use and easy to describe.
> > Mostly when users on site are describing the LEDs states to the
On Fri, Dec 27, 2013 at 12:24:22PM +, One Thousand Gnomes wrote:
> On Tue, 24 Dec 2013 21:36:01 +0530
> Viresh Kumar wrote:
>
> > Adding Dirk..
> >
> > On 24 December 2013 20:06, Josh Boyer wrote:
> > > Hi All,
> > >
> > > We've had a report [1] that the pstate driver causes KVM guests to
On 12/26/13 10:58, Joe Xue wrote:
Hi all,
I think Pavel's suggestion is a good idea, I'm starting to write another
trigger named Morse code trigger.
Those who don't know history are doomed to fail the class and have to
retake it with the same instructor next year:
On 12/26/13 20:13, Greg KH wrote:
On Thu, Dec 26, 2013 at 11:25:03AM +0800, Xishi Qiu wrote:
Add kmemcheck to Documentation/kernel-parameters.txt.
Signed-off-by: Xishi Qiu
---
Documentation/kernel-parameters.txt |7 +++
1 files changed, 7 insertions(+), 0 deletions(-)
This is
On Fri, Dec 27, 2013 at 06:32:24PM +0800, Gu Zheng wrote:
> Hi Matthew,
> On 12/26/2013 10:13 PM, Matthew Wilcox wrote:
>
> > On Thu, Dec 26, 2013 at 06:22:10PM +0800, Gu Zheng wrote:
> >> to the new free slot if it's smaller than 'next_free'. So that we can
> >> ensure that the slots before
On Fri, Dec 27, 2013 at 1:31 AM, Joe Xue wrote:
> echo "-.-. *"> patten
> - a long on then a off
> . a short on then a off
> space a long off
> * mean repeat the patten
> s mean indicate the patten just one time then stop
Why both "*" and
On 12/26/13 11:38, Alexander Holler wrote:
Hello,
I've just read Documentation/dynamic-debug-howto.txt (again) and I
wonder what the parameter -c for echo is for (found at lines 94 ff).
Neither echo from coreutils nor the buildin from bash do know the
parameter -c.
Huh. No idea.
Annotate
From: Scott Liu
This patch is for Elan eKTH Touchscreen product, I2C adpater module.
Signed-off-by: Scott Liu
---
drivers/input/touchscreen/Kconfig | 12 +
drivers/input/touchscreen/Makefile |1 +
drivers/input/touchscreen/elants_i2c.c | 1789
3
On Tue, 24 Dec 2013 21:36:01 +0530
Viresh Kumar wrote:
> Adding Dirk..
>
> On 24 December 2013 20:06, Josh Boyer wrote:
> > Hi All,
> >
> > We've had a report [1] that the pstate driver causes KVM guests to
> > fail to boot because of a divide error. See the backtrace below.
> >
> >
Dear Friend,
I received encouraging information about you and how trusts worthy you are. I
am delighted with such useful information. I am Foreign Operations Manager of
Banque Internationale du Burkina (BIB/UBA) Ouagadougou Burkina Faso.
I want to transfer US$10.5 Million to
On Wed, 25 Dec 2013 20:02:33 -0500
Joe Xue wrote:
> Hi,
>
> Yes, Morse code can indicate any means. But when we look at the LEDs, would
> we like to also have a Morse code book in hand?
>
> The burst led blink idea is because it is easy to use and easy to describe.
> Mostly when users on
From: Zhi Yong Wu
They were found when i review sched related src code.
Zhi Yong Wu (5):
sched, rt: move .switched_from out of the scope of CONFIG_SMP
sched, fair: fix the comment of move_tasks()
sched, fair: fix the typo in select_idle_sibling()
sched, fair: fix the comment of
From: Zhi Yong Wu
Signed-off-by: Zhi Yong Wu
---
kernel/sched/fair.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
index a82ae0a..db23d71 100644
--- a/kernel/sched/fair.c
+++ b/kernel/sched/fair.c
@@ -4191,7 +4191,7 @@
From: Zhi Yong Wu
Signed-off-by: Zhi Yong Wu
---
kernel/sched/fair.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
index db23d71..eaa1e91 100644
--- a/kernel/sched/fair.c
+++ b/kernel/sched/fair.c
@@ -4218,7 +4218,7 @@ done:
101 - 200 of 488 matches
Mail list logo
