On Mon, Jul 07, 2014 at 07:13:41PM +0100, Sitsofe Wheeler wrote:
> On Mon, Jul 07, 2014 at 04:54:20PM +, Haiyang Zhang wrote:
> >
> > > -Original Message-
> > > From: Sitsofe Wheeler [mailto:sits...@gmail.com]
> > > Sent: Sunday, July 6, 2014 4:18 PM
> > > To: Haiyang Zhang
> > > Cc:
This patch introduces two new device assignment functions
pci_sriov_assign_device(),
pci_sriov_deassign_device()
along with the existed one
pci_vfs_assigned()
They construct the VFs assignment management interface, used to assign/
deassign device to VM and query the VFs reference counter.
Current implementation of helper function pci_vfs_assigned() is a
little complex, to get sum of VFs that assigned to VM, access low
level configuration space register and then loop in traversing
device tree.
This patch introduces an atomic reference counter for VFs those
were assigned to VM in
Hi Linus !
Here are a few more powerpc fixes for 3.16
There's a small series of 3 patches that fix saving/restoring MMUCR2
when using KVM without which perf goes completely bonkers in the host
system. Another perf fix from Anton that's been rotting away in patchwork
due to my poor eyesight, a
On 07/11/2014 03:16 AM, Stephane Eranian wrote:
> On Mon, Jun 30, 2014 at 4:46 PM, Stephane Eranian wrote:
>>
>> This patch fixes the SNB-EP and IVT Cbox filter mapping
>> table. The table controls which filters are supported by
>> which events. There were several mistakes in those tables
>>
On Tue, 8 Jul 2014 09:24:08 +0200 (CEST), Nicolas Pitre
wrote:
> On Mon, 7 Jul 2014, Laura Abbott wrote:
>
> > Commit a67a6ed15513541579d38bcbd127e7be170710e5
> > (of: Check for phys_addr_t overflows in early_init_dt_add_memory_arch)
> > corrected early_init_dt_add_memory_arch to account for
Hi Greg,
Today's linux-next merge of the staging tree got a conflict in
drivers/staging/dgrp/dgrp_tty.c between commit e359a4e38d22 ("tty:
Remove tty_hung_up_p() tests from tty drivers' open()") from the tty
tree and commit 19b1e7695be8 ("staging: dgrp: remove driver") from the
staging tree.
I
On Thu, Jul 10, 2014 at 1:10 PM, Nick Krause wrote:
>>> Ok Randy ,
>>> Thanks for the help. Hope this message is better makes sense to me.
>>> Cheers Nick
>>
>> Yes, this is good. Thanks.
>>
>> --
>> ~Randy
> Here is my updated list of still failing builds. I am also this time
> attaching
On Wednesday 09 July 2014 06:40 PM, Grygorii Strashko wrote:
> This patch allows to create PHYs from DT in case
> if they are explicitly defined. The of_mdiobus_register() is
> used for such purposes.
>
> For backward compatibility, call of_mdiobus_register() only in case
> if at least one PHY's
On Wednesday 09 July 2014 06:40 PM, Grygorii Strashko wrote:
> The similar MDIO HW blocks is used by keystone 2 SoCs as
> in Davinci SoCs:
> - one in Gigabit Ethernet (GbE) Switch Subsystem
> See http://www.ti.com/lit/ug/sprugv9d/sprugv9d.pdf
> - one in 10 Gigabit Ethernet Subsystem
> See
On 07/10/2014 03:16 PM, Aravind Gopalakrishnan wrote:
PCI_DEVICE_ID_AMD_16H_NB_F4 can be obtained from it's
definition in pci_ids.h. So we don't have to define it
again here.
Signed-off-by: Aravind Gopalakrishnan
Applied to -next.
Thanks,
Guenter
--
To unsubscribe from this list: send the
Hi Tuomas,
On 11 July 2014 03:12, Tuomas Tynkkynen wrote:
> Add a new cpufreq driver for Tegra124. Instead of using the PLLX as
> the CPU clocksource, switch immediately to the DFLL. It allows the use
> of higher clock rates, and will automatically scale the CPU voltage as
> well. We also rely
Hi Jason,
Today's linux-next merge of the irqchip tree got a conflict in
arch/arm64/Kconfig between commit 875cbf3e4614 ("arm64: Add audit
support") from the arm64 tree and commit 021f653791ad ("irqchip:
gic-v3: Initial support for GICv3") from the irqchip tree.
I fixed it up (see below) and can
This bug can be trigger by L1 goes down directly w/ enable_shadow_vmcs.
[ 6413.158950] kvm: vmptrld (null)/7800 failed
[ 6413.158954] vmwrite error: reg 401e value 4 (err 1)
[ 6413.158957] CPU: 0 PID: 4840 Comm: qemu-system-x86 Tainted: G OE
3.16.0kvm+ #2
[
Just adding a simple if statement, which
verifies if actually card is loaded, if not
does not continue with the execution
of the snd_card_free.
Signed-off-by: Konstantinos Tsimpoukas
---
sound/pci/ice1712/ice1712.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git
The CPUfreq driver moves the cpufreq policy ownership between CPUs when
CPUs within a cluster (CPUs sharing same policy) go ONLINE/OFFLINE. When
moving policy ownership between CPUs, it also moves the cpufreq sysfs
directory between CPUs and also fixes up the symlinks of the other CPUs in
the
This patch introduces the use of managed interfaces like devm_clk_get
and does away with the clk_puts in the probe and remove functions. A
label is also done away with.
Signed-off-by: Himangi Saraogi
---
This is a follow up to ASoC: omap-dmic: use managed interfaces which
failed to apply as the
On Thu, Jul 10, 2014 at 10:06:27AM -0700, bseg...@google.com wrote:
> So, sched_clock(_cpu) can be arbitrarily far off of cfs_rq_clock_task, so you
> can't really do that. Ideally, yes, you would account for any time since
> the last update and account that time as !runnable. However, I don't
>
On 07/10/2014 08:38 PM, Richard Guy Briggs wrote:
> Commit
> fca460f h...@zytor.com 2012-02-19 07:56:26 -0800
> x32: Handle the x32 system call flag
>
> provided a method to multiplex architecture with the syscall number for X32
> calls.
>
> Commit
> 8b4b9f2 pmo...@redhat.com
s->maxdata for the do subdevice should be 1, however currently it is
being set to 0x. Fix this.
Signed-off-by: Chase Southwood
Cc: Ian Abbott
Cc: H Hartley Sweeten
---
This patch is at the end because I'm somewhat uncertain of its
correctness. Every other addi_apci_* driver with a
The dev->board_name is now initialized by the comedi core before calling
the(*attach) or (*auto_attach) function in a driver. As long as the driver
does no additional probing, it's no longer necessary initialize the board_name.
Signed-off-by: Chase Southwood
Cc: Ian Abbott
Cc: H Hartley Sweeten
There is no need to test whether devpriv is null in this function. The
check looks left over and we can just remove it.
Signed-off-by: Chase Southwood
Cc: Ian Abbott
Cc: H Hartley Sweeten
---
drivers/staging/comedi/drivers/addi_apci_1564.c | 12
1 file changed, 4 insertions(+),
Hi,
On Thu, Jul 10, 2014 at 6:45 PM, Javier Martinez Canillas
wrote:
>> I think when DVS gpio is used all the 8 voltage levels are fetched
>> from DT during booting and the registers are programmed accordingly.
>> Any further set/get_voltage just changes the GPIO lines.
>> Any reason why this
This value is only needed for subdevices that support async commands.
The comedi core will default the value to 1 when it is not initialized.
Signed-off-by: Chase Southwood
Cc: Ian Abbott
Cc: H Hartley Sweeten
---
drivers/staging/comedi/drivers/addi_apci_1564.c | 2 --
1 file changed, 2
This is a small patchset containing a handful of fixes to the ADDI-DATA
APCI1564 driver that I would like to get out of the way before I forget
to take care of them. From here, I will move to start fixing the
digital input/timer/counters/watchdog functionality of the board.
Chase Southwood (4):
On Thu, Jul 10, 2014 at 10:01:42AM -0700, bseg...@google.com wrote:
> > The problem with that is that last_update_time is measured in
> > clock_task, and you cannot transfer these values between CPUs.
> > clock_task can drift unbounded between CPUs.
>
> Yes, but we don't need to - we just use the
On Wed, Jul 9, 2014 at 11:28 PM, Julius Werner wrote:
> On Wed, Jul 9, 2014 at 3:01 AM, Vivek Gautam wrote:
>> Some quirky PHYs may require to be calibrated post the host
>> controller initialization.
>> The USB 3.0 DRD PHY on Exynos5420/5800 systems, coming along with
>> Synopsys's DWC3
This set reverts commit 8b4b9f2 which broke audit and potentially other users
of syscall_get_nr() which depend on that call as named without being overloaded
by architecture bits. It will satisfy other regular users of syscall_get_nr()
and syscall_get_arch() without changing the seccomp interface
Hi Julius,
On Wed, Jul 9, 2014 at 11:26 PM, Julius Werner wrote:
> On Wed, Jul 9, 2014 at 3:01 AM, Vivek Gautam wrote:
>> The host controller by itself may sometimes need to handle PHY
>> and/or calibrate some of the PHY settings to get full support out
>> of the PHY controller. The PHY core
Add a definition for 32-bit native system calls under 64-bit x86 architectures.
This is distict from 32-bit emulation under 64-bit x86 architectures.
Cc: Paul Moore
Cc: Eric Paris
Cc: Al Viro
Cc: Will Drewry
Cc: H. Peter Anvin
Signed-off-by: Richard Guy Briggs
---
This reverts commit 8b4b9f27e57584f3d90e0bb84cf800ad81cfe3a1.
which broke audit and potentially other users of syscall_get_nr() which depend
on that call as named without being overloaded by architecture bits.
This patch along with
seccomp: give BPF x32 bit when restoring x32 filter
will
Commit
fca460f h...@zytor.com 2012-02-19 07:56:26 -0800
x32: Handle the x32 system call flag
provided a method to multiplex architecture with the syscall number for X32
calls.
Commit
8b4b9f2 pmo...@redhat.com 2013-02-15 12:21:43 -0500
x86: remove the x32 syscall
On 07/10/2014 06:13 PM, Greg KH wrote:
> On Tue, Jul 01, 2014 at 10:15:34AM -0500, Alex Elder wrote:
>> Currently the Synopsys DesignWare 8250 driver assumes its UART clock
>> runs at a fixed rate. If a "real" clock was set up using the common
>> clock framework, and that clock's rate is
On 2014/7/11 10:33, Alex Williamson wrote:
On Fri, 2014-07-11 at 10:29 +0800, ethan zhao wrote:
On 2014/7/11 10:22, Alex Williamson wrote:
On Fri, 2014-07-11 at 10:10 +0800, ethan zhao wrote:
Alex,
Thanks for your reviewing, when I create the patch order, I thought
about the question
When the shrinker doesn't free any memory, don't spew over and over
into the logs. My fuzz tester hits this quite easily, resulting
in dozens of instances of this printk when memory runs low, filling
dmesg, when there's not even any graphical stuff going on, so the
situation would never change.
On 07/11/2014 11:50 AM, Ben Skeggs wrote:
On Fri, Jul 11, 2014 at 12:35 PM, Alexandre Courbot wrote:
On 07/10/2014 09:58 PM, Daniel Vetter wrote:
On Tue, Jul 08, 2014 at 05:25:57PM +0900, Alexandre Courbot wrote:
page_to_phys() is not the correct way to obtain the DMA address of a
buffer
On Fri, Jul 11, 2014 at 12:35 PM, Alexandre Courbot wrote:
> On 07/10/2014 09:58 PM, Daniel Vetter wrote:
>>
>> On Tue, Jul 08, 2014 at 05:25:57PM +0900, Alexandre Courbot wrote:
>>>
>>> page_to_phys() is not the correct way to obtain the DMA address of a
>>> buffer on a non-PCI system. Use the
On Thu, 2014-07-10 at 18:25 +1000, NeilBrown wrote:
> On Thu, 10 Jul 2014 15:43:40 +0800 Ian Kent wrote:
>
> > On Thu, 2014-07-10 at 09:41 +1000, NeilBrown wrote:
> > > autofs4 currently doesn't support RCU-walk - it immediately
> > > aborts any attempt at RCU-walk to force REF-walk for path
Since upgrading from 3.12.24 kernel to 3.14.10, and today, .12 kernel
log and dmesg are flooded with constant messages
option1 ttyUSB0: option_instat_callback: error -2
The device still works, it sends and receives SMS's as well,
I tried setting verbose usb debug to see if it offers any more
This is the driver for the Dialog DA9211 Multi-phase 12A DC-DC Buck
Converter regulator. It communicates via an I2C bus to the device.
Signed-off-by: James Ban
---
This patch is relative to linux-next repository tag next-20140710.
Changes in V5:
- Use devm_regulator_register instead
> From: Sebastian Reichel [mailto:s...@kernel.org]
> Sent: Tuesday, July 08, 2014 9:26 PM
> To: Tc, Jenny
> Cc: linux-kernel@vger.kernel.org; Dmitry Eremin-Solenikov; Pavel Machek;
> Stephen
> Rothwell; Anton Vorontsov; David Woodhouse; David Cohen; Pallala, Ramakrishna
> Subject: Re: [PATCH 3/4]
On Thu, Jul 10, 2014 at 10:16:56AM -0700, Havard Skinnemoen wrote:
> Date: Thu, 10 Jul 2014 10:16:56 -0700
> From: Havard Skinnemoen
> To: "Chen, Gong"
> Cc: Borislav Petkov , Tony Luck , Linux
> Kernel , Ewout van Bekkum
> Subject: Re: [PATCH 1/6] x86-mce: Modify CMCI poll interval to adjust
On 07/10/2014 10:04 PM, Daniel Vetter wrote:
On Tue, Jul 08, 2014 at 05:25:59PM +0900, Alexandre Courbot wrote:
On architectures for which access to GPU memory is non-coherent,
caches need to be flushed and invalidated explicitly when BO control
changes between CPU and GPU.
This patch adds
On 2014年07月09日 15:08, Jerome FORISSIER wrote:
On 30-Jun-14 10:03, Zhou Wang wrote:
Signed-off-by: Zhou Wang
---
arch/arm/boot/dts/hip04.dtsi | 31 +++
1 file changed, 31 insertions(+)
diff --git a/arch/arm/boot/dts/hip04.dtsi b/arch/arm/boot/dts/hip04.dtsi
Fix breakage introduced by
commit c557d392fbf5badd693ea1946a4317c87a26a716,
'serial: Test for no tx data on tx restart'.
Signed-off-by: Peter Hurley
---
drivers/tty/serial/imx.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/tty/serial/imx.c
On 2014年07月11日 03:32, Moore, Robert wrote:
> Since what is returned by this interface is essentially a piece of
> information about the particular GPE, I think that it might be better to
> generalize this interface to a "GetInfo" type of interface that returns a few
> pieces of information
On 07/10/2014 09:58 PM, Daniel Vetter wrote:
On Tue, Jul 08, 2014 at 05:25:57PM +0900, Alexandre Courbot wrote:
page_to_phys() is not the correct way to obtain the DMA address of a
buffer on a non-PCI system. Use the DMA API functions for this, which
are portable and will allow us to use other
On Fri, 2014-07-11 at 10:29 +0800, ethan zhao wrote:
> On 2014/7/11 10:22, Alex Williamson wrote:
> > On Fri, 2014-07-11 at 10:10 +0800, ethan zhao wrote:
> >> Alex,
> >> Thanks for your reviewing, when I create the patch order, I thought
> >> about the question you concerned for
> >> quit a
I decided to play with my snowball board as that's the easiest arm
board I have to do testing on, and it was reported to me that I broke
function graph tracing on the arm boards. But I haven't booted my
snowball since 3.8. When I tried with the latest kernel, it didn't give
me *any* output. I
On 2014/7/11 10:22, Alex Williamson wrote:
On Fri, 2014-07-11 at 10:10 +0800, ethan zhao wrote:
Alex,
Thanks for your reviewing, when I create the patch order, I thought
about the question you concerned for
quit a while, make every patch be independent to each other as possible
as I
On Sun, 6 Jul 2014 10:58:41 +0200
Geert Uytterhoeven wrote:
> If CONFIG_SOLO6X10=y, but CONFIG_BITREVERSE=m:
>
> drivers/built-in.o: In function `solo_osd_print':
> (.text+0x1c7a1f): undefined reference to `byte_rev_table'
> make: *** [vmlinux] Error 1
>
> Reported-by: kbuild test
(2014/07/11 6:44), Jiri Kosina wrote:
> On Thu, 10 Jul 2014, Josh Poimboeuf wrote:
>
>> I did some testing with kpatch and I found one minor issue. The dynamically
>> allocated trampoline seems to confuse dump_stack() somewhat.
>>
>> I added a dump_stack() call in my ftrace_ops callback function
I noticed this change between 3.14.3-rt5 and 3.14.10-rt7:
--- debian/patches/features/all/rt/random-make-it-work-on-rt.patch
(revision 21522)
+++ debian/patches/features/all/rt/random-make-it-work-on-rt.patch
(working copy)
[...]
a/kernel/irq/manage.c
-+++ b/kernel/irq/manage.c
On Fri, 2014-07-11 at 10:10 +0800, ethan zhao wrote:
> Alex,
> Thanks for your reviewing, when I create the patch order, I thought
> about the question you concerned for
> quit a while, make every patch be independent to each other as possible
> as I could, so we can do bisect when hit
>
MAP10 command with '0x2000' data sets up a read-ahead/write access.
Signed-off-by: Masahiro Yamada
---
drivers/mtd/nand/denali.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/mtd/nand/denali.c b/drivers/mtd/nand/denali.c
index 9f2012a..7c1c1ab 100644
---
Alex,
Thanks for your reviewing, when I create the patch order, I thought
about the question you concerned for
quit a while, make every patch be independent to each other as possible
as I could, so we can do bisect when hit
problem.
I manage to take more time to figure out better patch
From: Addy Ke
Suggested-by: Mark Brown
Signed-off-by: Addy Ke
---
drivers/spi/spi-rockchip.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/spi/spi-rockchip.c b/drivers/spi/spi-rockchip.c
index a8866c9..cb8fd6f 100644
--- a/drivers/spi/spi-rockchip.c
+++
From: Addy Ke
Suggested-by: Jonas Gorski
Signed-off-by: Addy Ke
---
drivers/spi/spi-rockchip.c | 7 +--
1 file changed, 1 insertion(+), 6 deletions(-)
diff --git a/drivers/spi/spi-rockchip.c b/drivers/spi/spi-rockchip.c
index 09c690c..a8866c9 100644
--- a/drivers/spi/spi-rockchip.c
+++
From: Addy Ke
Suggested-by: Mark Brown
Signed-off-by: Addy Ke
---
drivers/spi/spi-rockchip.c | 41 +++--
1 file changed, 23 insertions(+), 18 deletions(-)
diff --git a/drivers/spi/spi-rockchip.c b/drivers/spi/spi-rockchip.c
index 72fb287..8c24708 100644
From: Addy Ke
Suggested-by: Mark Brown
Signed-off-by: Addy Ke
---
drivers/spi/spi-rockchip.c | 24 +++-
1 file changed, 19 insertions(+), 5 deletions(-)
diff --git a/drivers/spi/spi-rockchip.c b/drivers/spi/spi-rockchip.c
index 8c24708..09c690c 100644
---
From: Addy Ke
These patches based on:
- git: kernel/git/broonie/spi.git
- branch: topic/rockchip
- commit: c15369087ae5c7db7f3e3604822eac6ab87429bd
Addy Ke (4):
spi/rockchip: cleanup some coding issues and uncessary output
spi/rockchip: call wait_for_idle() for the transfer to complete
Hello Amit,
On 07/10/2014 12:08 PM, amit daniel kachhap wrote:
> On Fri, Jul 4, 2014 at 3:25 PM, Javier Martinez Canillas
> wrote:
>> MAX77686 PMIC support Dyamic Voltage Scaling (DVS) on a set
>> of Buck regulators. A number of GPIO are connected to these
>> lines and are requested by the mfd
On Fri, Jul 11, 2014 at 11:49 AM, Alexandre Courbot wrote:
> On 07/10/2014 06:43 PM, Peter De Schrijver wrote:
>>
>> On Thu, Jul 10, 2014 at 09:34:34AM +0200, Alexandre Courbot wrote:
>>>
>>> This series adds support for reclocking on GK20A. The first two patches
>>> touch
>>> the clock subsystem
On 07/10/2014 06:43 PM, Peter De Schrijver wrote:
On Thu, Jul 10, 2014 at 09:34:34AM +0200, Alexandre Courbot wrote:
This series adds support for reclocking on GK20A. The first two patches touch
the clock subsystem to allow GK20A to operate, by making the presence of the
thermal and voltage
Hi Boris,
On 07/11/2014 03:59 AM, Boris BREZILLON wrote:
Add ethernet-phy nodes and specify phy interrupt (connected to pin PB25)
and board specific timing configs.
Atmel has two different HW designs for its CPU modules: the first one
(produced by Embest) is connecting PHYAD[0-2] pins to pull
Since there's no 0th patch, I guess I'll comment here. This series is
not bisectable, patch 1 breaks the existing implementation. I'd
suggest:
patch 1 - fix i40e
patch 2 - create assign/deassign that uses dev_flags
patch 3 - convert users to new interface
patch 4 - convert interface to use
Hello Amit,
On 07/10/2014 11:59 AM, amit daniel kachhap wrote:
> On Sat, Jul 5, 2014 at 1:54 AM, Javier Martinez Canillas
> wrote:
>> Some regulators on the MAX77686 PMIC have Dynamic Voltage Scaling
>> (DVS) support that allows output voltage to change dynamically.
>>
>> For MAX77686, these
On 07/10/2014 06:50 PM, Mikko Perttunen wrote:
Does GK20A itself have any kind of thermal protection capabilities?
Upstream SOCTHERM support is not yet available (though I have a driver
in my tree), so we are thinking of disabling CPU DVFS on boards that
don't have always-on active cooling for
Hi Ben,
On 07/11/2014 10:07 AM, Ben Skeggs wrote:
On Thu, Jul 10, 2014 at 5:34 PM, Alexandre Courbot wrote:
This series adds support for reclocking on GK20A. The first two patches touch
the clock subsystem to allow GK20A to operate, by making the presence of the
thermal and voltage devices
Hi Linus,
Nothing too scary, we have one outstanding i915 regression but Daniel has
promised the fix as soon as he's finished testing it a bit.
Fixes for the main x86 drivers:
radeon: dpm fixes, displayport regression fix
i915: quirks for backlight regression, edp reboot fix, valleyview black
In alarmtimer_suspend(), the error after rtc_read_time() is not checked.
If rtc device fail to read rtc time, we cannot ensure the following process.
Furthermore, the return value of rtc_timer_start() needs to distinguish
-ETIME and other rtc device error. If the error is relevant to rtc device,
On Mon, Jun 23, 2014 at 1:57 PM, Benjamin Tissoires
wrote:
> Hi,
>
> This patch series aims at simplifying the handling of Wacom devices from the
> user
> space point of view. As mentioned in the commit message from 1/5, the pad data
> are interleaved into the stylus input for some devices, and
== (circ)->tail)
^
Caused by commit c557d392fbf5 ("serial: Test for no tx data on tx
restart"). That can't have been build tested :-(
I have used the tty.current tree from next-20140710 for today.
--
Cheers,
Stephen Rothwell
On Wed, Jul 9, 2014 at 3:56 PM, Paul E. McKenney
wrote:
> OK, so ->dynticks_snap is accessed by only one task, namely the
> corresponding RCU grace-period kthread. So it can be accessed without
> any atomic instructions or memory barriers, since all accesses to it are
> single-threaded. On the
On Wed, Jul 2, 2014 at 4:33 PM, Jason Gerecke wrote:
> On Mon, Jun 30, 2014 at 2:26 PM, Benjamin Tissoires
> wrote:
>> Hi guys,
>>
>> this patch series is a cleanup for the Wacom USB driver.
>>
>> I started working on this topic when I saw patches floating around which
>> implemented a report
Now that we can tolerate extra things dangling off the end of the
vdso image, we can strip the vdso the old fashioned way rather than
using an overcomplicated custom stripping algorithm.
This is a partial reversion of:
6f121e5 x86, vdso: Reimplement vdso.so preparation in build-time C
The fancy ideas of aggressively stripping the vdso and placing the
vvar data after the vdso have been considerably more painful than I
hoped. This reverts to using objcopy -S to strip the vdso (thus
eliminating the whole fake section mechanism and all of its
attendent build-time fragility, I
Putting the vvar area after the vdso text is rather complicated: it
only works of the total length of the vdso text mapping is known at
vdso link time, and the linker doesn't allow symbol addresses to
depend on the sizes of non-allocatable data after the PT_LOAD
segment.
Moving the vvar area
On Mon, Jun 30, 2014 at 2:26 PM, Benjamin Tissoires
wrote:
> This removes an USB dependency and is more accurate: the computed pktlen
> is the actual maximum size of the reports forwarded by the device.
>
> Given that the pktlen is correctly computed/validated, we can store it now
> in the
On Thu, Jul 10, 2014 at 5:34 PM, Alexandre Courbot wrote:
> This series adds support for reclocking on GK20A. The first two patches touch
> the clock subsystem to allow GK20A to operate, by making the presence of the
> thermal and voltage devices optional, and allowing pstates to be provided
>
Use poll(2) to wait for a message. If a client/server cannot send a message for
any reasons, the current server/client will wait in a blocking read operation.
So, we use poll(2) for avoiding remaining in a blocking state.
Changes in V4: Change the argument of tracecmd_msg_recv_wait()
Hi Steven,
This is a v4 patch set to support the feature which guests send trace data via
virtio. (Previous patch set is here: https://lkml.org/lkml/2013/12/16/688)
Any features in this V4 patch series are not changed from previous version.
I fixed some typos, rebased for current version, and
Add --virt option for record mode for a virtualization environment.
If we use this option on a guest, we can send trace data in low-overhead.
This is because guests can send trace data to a host without copying the data
by using splice(2).
The format is:
trace-cmd record --virt -e sched*
Apply trace-msg protocol for communication between a server and clients.
Currently, trace-listen(server) and trace-record -N(client) operate as follows:
listen to socket fd
connect to socket fd
accept the client
send
Add --dom option which makes a domain directory to virt-server. When a user
already knows domain name of a guest before running virt-server, trace-cmd
should automatically set up I/Fs of the guest. By adding --dom option,
trace-cmd creates a domain directory with 0710 and qemu group.
This patch
Add the virt-server mode for a virtualization environment based on the listen
mode for networking. This mode works like client/server mode over TCP/UDP,
but it uses virtio-serial channel instead of IP network. Using networking for
collecting trace data of guests is generally high overhead caused
Hello Linus,
On 07/10/2014 11:46 AM, Linus Walleij wrote:
> On Fri, Jul 4, 2014 at 10:24 PM, Javier Martinez Canillas
> wrote:
>
>> Some regulators on the MAX77686 PMIC have Dynamic Voltage Scaling
>> (DVS) support that allows output voltage to change dynamically.
>>
>> For MAX77686, these
(2014/07/10 18:26), Igor Mammedov wrote:
On Thu, 10 Jul 2014 17:41:50 +0900
Yasuaki Ishimatsu wrote:
llc_shared_map is not cleared even if CPU is offline or hot removed.
So when hot-plugging CPU and assigning new CPU number to hot-added CPU,
the mask has wrong value. The mask is used by CSF
New VFs reference counter mechanism and VFs assignment helper functions are
introduced to
PCI SRIOV, use them instead of manipulating device flag directly.
Signed-off-by: Ethan Zhao
---
virt/kvm/assigned-dev.c |2 +-
virt/kvm/iommu.c|4 ++--
2 files changed, 3 insertions(+), 3
New VFs reference counter mechanism and VFs assignment helper functions are
introduced to
PCI SRIOV, use them instead of manipulating device flag directly.
Signed-off-by: Ethan Zhao
---
drivers/xen/xen-pciback/pci_stub.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git
Current implementation of helper function pci_vfs_assigned() is a little
complex, to
get sum of VFs that assigned to VM, access low level configuration space
register and
then loop in traversing device tree.
This patch introduce an atomic reference counter for VFs that assigned to VM in
struct
New VFs reference counter mechanism and VFs assignment helper functions are
introduced to
PCI SRIOV, use them instead of manipulating device flag directly.
Signed-off-by: Ethan Zhao
---
drivers/net/ethernet/intel/i40e/i40e_virtchnl_pf.c | 17 ++---
1 files changed, 2
On Thu, 10 Jul 2014 17:15:49 -0700 Guenter Roeck wrote:
> Error on my part - I thought lower numbers would
> have higher priority, but after looking into the code again that
> is wrong.
You shouldn't have needed to look into the code :( Maybe a
documentation patch for notifier_block.priority
Hi,
On Tue, Jul 8, 2014 at 10:18 AM, Liviu Dudau wrote:
> On Sun, Jul 06, 2014 at 04:23:43PM +0100, Rob Herring wrote:
>> On Tue, Jul 1, 2014 at 1:43 PM, Liviu Dudau wrote:
>> > This is my resurected attempt at adding support for generic PCI host
>> > bridge controllers that make use of device
Hello Rob,
On Thu, Jul 10, 2014 at 1:01 PM, Rob Jones wrote:
>
>
> On 10/07/14 10:21, Linus Walleij wrote:
>>
>> On Wed, Jul 9, 2014 at 1:18 PM, Rob Jones
>> wrote:
>>
>>> Please note that I submitted a patch on 02/07/14 to create this
>>> function which was acked by Linus Walleij on 05/07/14.
Hi Jianqun,
On Fri, 11 Jul 2014 08:07:20 +0800 Jianqun wrote:
>
> Is it caused by the headfile ?
> #include
>
> Adviced by the maintainers, I tried not to include the headfile one by one,
> then to compile
> driver each time, I found that is success to compile it without module.h, of
>
On Mon, Jun 23, 2014 at 1:57 PM, Benjamin Tissoires
wrote:
> Currently, the pad events are sent through the stylus input device
> for the Intuos/Cintiqs, and through the touch input device for the
> Bamboos.
>
> To differentiate the buttons pressed on the pad from the ones pressed
> on the
On 07/10/2014 04:09 PM, Andrew Morton wrote:
On Tue, 8 Jul 2014 20:37:56 -0700 Guenter Roeck wrote:
The existing mechanisms have a number of drawbacks. Typically only one scheme
to restart the system is supported (at least if arm_pm_restart is used).
At least in theory there can be mutliple
Dear Heiko:
FYI
On 2014年07月11日 08:07, Jianqun wrote:
> Hi Heiko:
>
> Is it caused by the headfile ?
> #include
>
> Adviced by the maintainers, I tried not to include the headfile one by one,
> then to compile
> driver each time, I found that is success to compile it without module.h, of
>
On Mon, Jun 30, 2014 at 2:26 PM, Benjamin Tissoires
wrote:
> Wacom tablets can share different physical sensors on one physical device.
> These are called siblings in the code. The current way of implementation
> relies on the USB topology to be able to share data amongs those sensors.
>
> We can
1 - 100 of 1826 matches
Mail list logo
