On 05/10/2016 01:03 AM, Alex Williamson wrote:
> On Wed, 4 May 2016 14:06:19 +0200
> Eric Auger wrote:
>
>> Hi Alex,
>> On 05/04/2016 01:54 PM, Eric Auger wrote:
>>> This patch allows the user-space to retrieve the MSI geometry. The
>>> implementation is based on capability chains, now also added
Neither APICv nor AVIC actually need the first argument of
hwapic_isr_update, but the vCPU makes more sense than passing the
pointer to the whole virtual machine! In fact in the APICv case it's
just because the vCPU is used implicitly, through the loaded VMCS.
The second argument instead is named
On Mon, 9 May 2016 12:53:37 -0500
Reza Arbab wrote:
> Add move_pfn_range(), a wrapper to call move_pfn_range_left() or
> move_pfn_range_right().
>
> No functional change. This will be utilized by a later patch.
>
> Signed-off-by: Reza Arbab
Looks good to me.
Reviewed-by: Yasuaki Ishimatsu
On Tue, May 10, 2016 at 9:30 AM, Cyrill Gorcunov wrote:
> On Tue, May 10, 2016 at 09:07:49AM -0700, Andy Lutomirski wrote:
>> Hi all-
>>
>> I'm trying to get rid of x86's dynamic TASK_SIZE and just redefine it
>> to TASK_SIZE_MAX. So far, these are the TASK_SIZE users that actually
>> seem to car
On 10/05/16 16:51, Shyam Saini wrote:
Fixed following checkpatch.pl warnings
WARNING: Prefer WRITE_ONCE(, ) over ACCESS_ONCE() =
WARNING: Prefer READ_ONCE() over ACCESS_ONCE()
Signed-off-by: Shyam Saini
---
drivers/staging/comedi/comedi_fops.c | 12 ++--
1 file changed, 6 insertion
On 05/10/2016 06:26 AM, Sergei Shtylyov wrote:
On 5/10/2016 2:46 AM, David Lechner wrote:
The CFGCHIP registers are used by a number of devices, so using a syscon
device to share them. The first consumer of this will by the
phy-da8xx-usb
driver.
Signed-off-by: David Lechner
[...]
diff --git
On Tue, 2016-05-10 at 12:30 -0400, Tejun Heo wrote:
> Hello,
>
> On Tue, May 10, 2016 at 11:34:40AM +0530, Vinod Koul wrote:
> >
> > >
> > > slave-dma [1], branch topic/dw. But I think Vinod can tell us
> > > which
> > > tag/branch will be immutable. Vinod?
> > Please use branch topic/dw. I will
For ethernet devices, net_device.name will be eth%d before
register_netdev() is called. Don't print the net_device name until
the format string is replaced.
Cc: Robert Jarzmik
Cc: Barry Song
Cc: Marcel Ziswiler
Cc: net...@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Signed-off-by: Harvey H
Hello,
On Tue, May 10, 2016 at 07:28:08PM +0300, Konstantin Khlebnikov wrote:
> On 10.05.2016 11:21, Konstantin Khlebnikov wrote:
> >I've got plenty warnings, bugs and oops around trivial use of
> >mod_delayed_work in drivers/infiniband/core/addr.c
>
> Looks like problem in mod_delayed_work_on w
>> (3) Also we may not want to count at every sched_in and sched_out
>> because the MSR reads involve quite a bit of overhead.
>
> Every single other PMU driver just does this; why are you special?
They just have to read a register. We have to write the IA32_EM_EVT_SEL MSR
and then read fro
Hi Alex,
On 05/10/2016 12:49 AM, Alex Williamson wrote:
> On Wed, 4 May 2016 11:54:18 +
> Eric Auger wrote:
>
>> This patch allows the user-space to retrieve the MSI geometry. The
>> implementation is based on capability chains, now also added to
>> VFIO_IOMMU_GET_INFO.
>>
>> The returned in
When a partition is not aligned by 4KB, mount -o dax succeeds,
but any read/write access to the filesystem fails, except for
metadata update.
Call bdev_dax_supported() to perform proper precondition checks
which includes this partition alignment check.
Reported-by: Micah Parrish
Signed-off-by: T
When a partition is not aligned by 4KB, mount -o dax succeeds,
but any read/write access to the filesystem fails, except for
metadata update. Add alignment check to ext4, ext2, and xfs.
- Patch 1-2 add bdev_dax_supported() which performs all the checks
necessary for dax mount.
- Patch 3-5 chang
On Tue, May 10, 2016 at 06:29:00PM +0200, Borislav Petkov wrote:
> Also, please snip the mail text you're quoting if you're not going to
> refer to it. Like I just did.
Ok :-)
On 05/10/2016 10:13 AM, Jon Hunter wrote:
On 09/05/16 16:15, Jon Hunter wrote:
Support for SD cards is not working on the Tegra30 Beaver board and on
boot the following error message is seen if an SD card is present:
mmc0: error -110 whilst initialising SD card
In addition to this, Tegra30
In preparation of moving DAX capability checks to the block layer
from filesystem code, add a VFS message interface that aligns with
filesystem's message format.
For instance, a vfs_msg() message followed by XFS messages in case
of a dax mount error may look like:
VFS (pmem0p1): error: unaligne
When a partition is not aligned by 4KB, mount -o dax succeeds,
but any read/write access to the filesystem fails, except for
metadata update.
Call bdev_dax_supported() to perform proper precondition checks
which includes this partition alignment check.
Signed-off-by: Toshi Kani
Reviewed-by: Jan
blkdev_dax_capable() is similar to bdev_dax_supported(), but needs
to remain as a separate interface for checking dax capability of
a raw block device.
Rename and relocate blkdev_dax_capable() to keep them maintained
consistently, and call bdev_direct_access() for the dax capability
check.
There
On 10.05.2016 11:21, Konstantin Khlebnikov wrote:
I've got plenty warnings, bugs and oops around trivial use of mod_delayed_work
in drivers/infiniband/core/addr.c
Looks like problem in mod_delayed_work_on was hidden because add_timer is equal
to mod_timer
but Sasha accidentally backported 874
When a partition is not aligned by 4KB, mount -o dax succeeds,
but any read/write access to the filesystem fails, except for
metadata update.
Call bdev_dax_supported() to perform proper precondition checks
which includes this partition alignment check.
Signed-off-by: Toshi Kani
Reviewed-by: Chri
On May 10 2016 or thereabouts, Fabio Estevam wrote:
> On Tue, May 10, 2016 at 12:37 PM, Benjamin Tissoires
> wrote:
>
> > @@ -92,7 +93,7 @@ soc_button_device_create(struct platform_device *pdev,
> > continue;
> >
> > gpio = soc_button_lookup_gpio(&pdev->dev
DAX imposes additional requirements to a device. Add
bdev_dax_supported() which performs all the precondition checks
necessary for filesystem to mount the device with dax option.
Also add a new check to verify if a partition is aligned by 4KB.
When a partition is unaligned, any dax read/write acc
On Tue, May 10, 2016 at 09:07:49AM -0700, Andy Lutomirski wrote:
> Hi all-
>
> I'm trying to get rid of x86's dynamic TASK_SIZE and just redefine it
> to TASK_SIZE_MAX. So far, these are the TASK_SIZE users that actually
> seem to care about the task in question:
>
> get_unmapped_area. This is
Hello,
On Tue, May 10, 2016 at 11:34:40AM +0530, Vinod Koul wrote:
> > slave-dma [1], branch topic/dw. But I think Vinod can tell us which
> > tag/branch will be immutable. Vinod?
>
> Please use branch topic/dw. I will not rebase this before sending to Linus.
Okay, pulled topic/dw into libata/fo
On Tue, May 10, 2016 at 08:59:43AM -0700, Yu-cheng Yu wrote:
> This is actually a patch of Fenghua's, but I re-based it.
> I will fix it.
Then please take a look at Documentation/SubmittingPatches too.
Also, please snip the mail text you're quoting if you're not going to
refer to it. Like I just
On Tue, May 10, 2016 at 05:25:36PM +0900, Yoshinori Sato wrote:
> On Wed, 04 May 2016 12:10:05 +0900,
> Rich Felker wrote:
> >
> > On Sun, May 01, 2016 at 02:08:29PM +0900, Yoshinori Sato wrote:
> > > Changes bellow
> > > - FDT setup timing fix.
> > > - chosen/bootargs support.
> > > - zImage supp
On Tue, May 10, 2016 at 04:43:05PM +0200, Paolo Bonzini wrote:
> That was actually our suggestion. Despite the long names, the lines do
> not come out too long because the masks are only used for writing
> fields, not very much for reading them (e.g. in complex "if" conditions).
Sure but how can
The GSBASE upper limit exists to prevent user code from confusing
the paranoid idtentry path. The FSBASE upper limit is just for
consistency. There's no need to enforce a smaller limit for 32-bit
tasks.
Just use TASK_SIZE_MAX. This simplifies the logic and will save a
few bytes of code.
Signed
On Tue, May 10, 2016 at 9:26 PM, Stephen Warren wrote:
> On 05/09/2016 09:29 PM, Jassi Brar wrote:
>
>> Some controllers need a mask/list of destination cpus, to which the
>> irq is raised, written to some 'data' register. You too probably need
>> to program the destination "id" in the controller?
On 09/05/16 16:15, Jon Hunter wrote:
> Support for SD cards is not working on the Tegra30 Beaver board and on
> boot the following error message is seen if an SD card is present:
>
> mmc0: error -110 whilst initialising SD card
>
> In addition to this, Tegra30 is also randomly hanging during sy
Paolo Valente writes:
> When a bio is split, the newly created bio must be associated with the
> same blkcg as the original bio (if BLK_CGROUP is enabled). If this
> operation is not performed, then the new bio is not associated with
> any group, and the group of the current task is returned when
Hi Alex,
On 05/10/2016 12:49 AM, Alex Williamson wrote:
> On Wed, 4 May 2016 11:54:16 +
> Eric Auger wrote:
>
>> On x86 IRQ remapping is abstracted by the IOMMU. On ARM this is abstracted
>> by the msi controller. vfio_safe_irq_domain allows to check whether
>> interrupts are "safe" for a gi
On Tue, May 10, 2016 at 8:40 AM, Ruslan Kabatsayev
wrote:
> On Tue, May 10, 2016 at 6:23 PM, Andy Lutomirski wrote:
>> Anyway, what kernel are you on? I think I fixed your specific issue in:
>>
>> commit 27747f8bc355a2808ca9e490ab6866acd85b4c16
>> Author: Andy Lutomirski
>> Date: Thu Jul 30 2
From: Charanya
The Data loss was happening with current QCOM MSM serial driver during
large file transfer due to simultaneous enabling of both UART and
DMA interrupt. When UART operates in DMA mode, RXLEV (Rx FIFO over
watermark) or RXSTALE (stale interrupts) should not be enabled,
since these co
On Tue, 2016-05-10 at 18:03 +0200, Paolo Abeni wrote:
> If a single core host is under network flood, i.e. ksoftirqd is
> scheduled and it eventually (after processing ~640 packets) will let the
> user space process run. The latter will execute a syscall to receive a
> packet, which will have to d
On Tue, May 10, 2016 at 07:01:03PM +0300, Andy Shevchenko wrote:
> On Tue, 2016-05-10 at 21:26 +0530, Vinod Koul wrote:
> > On Wed, May 04, 2016 at 10:29:39PM +0300, Andy Shevchenko wrote:
> > >
> > > When check for capabilities recognize slave support by eother
> > > DMA_SLAVE or
> >
Hi all-
I'm trying to get rid of x86's dynamic TASK_SIZE and just redefine it
to TASK_SIZE_MAX. So far, these are the TASK_SIZE users that actually
seem to care about the task in question:
get_unmapped_area. This is used by mmap, mremap, exec, uprobe XOL,
and maybe some other things.
- mmap,
On Tue, 2016-05-10 at 21:26 +0530, Vinod Koul wrote:
> On Wed, May 04, 2016 at 10:29:39PM +0300, Andy Shevchenko wrote:
> >
> > When check for capabilities recognize slave support by eother
> > DMA_SLAVE or
> ^^^
> typo
Indeed, thanks.
Do
On Tue, May 10, 2016 at 07:00:23PM +0300, Andy Shevchenko wrote:
> On Tue, 2016-05-10 at 21:29 +0530, Vinod Koul wrote:
> > On Wed, May 04, 2016 at 10:29:40PM +0300, Andy Shevchenko wrote:
> > >
> > > Rename cmd_pause to cmd_suspend to be clear that latter capability
> > > reflects
> > > pause AND
From: John Crispin
Date: Tue, 10 May 2016 07:08:39 +0200
> @@ -236,7 +247,8 @@ static int mtk_phy_connect(struct mtk_mac *mac)
> mac->phy_dev->autoneg = AUTONEG_ENABLE;
> mac->phy_dev->speed = 0;
> mac->phy_dev->duplex = 0;
> - mac->phy_dev->supported &= PHY_BASIC_FEATURES;
This fixes the following sparse warnings:
drivers/gpu/drm/rockchip/rockchip_drm_fb.c:32:23: warning: symbol
'rockchip_fb_get_gem_obj' was not declared. Should it be static?
drivers/gpu/drm/rockchip/rockchip_drm_fb.c:315:24: warning: symbol
'rockchip_drm_framebuffer_init' was not declared. Should
Combined with the previous commit, this fixes all of the sparse warnings
in drm/rockchip.
Signed-off-by: John Keeping
---
drivers/gpu/drm/rockchip/rockchip_drm_drv.c | 4 ++--
drivers/gpu/drm/rockchip/rockchip_drm_fb.c | 6 +++---
drivers/gpu/drm/rockchip/rockchip_drm_vop.c | 4 ++--
drivers/gp
> On Tue, May 10, 2016 at 06:18:10AM +0200, Volker Lendecke wrote:
> > On Tue, May 10, 2016 at 12:02:33AM +0200, Andreas Gruenbacher wrote:
> > > What more can I do to finally get this merged?
> >
> > While I am not the one to comment on kernel specifics, from a pure
> > Samba user space perspectiv
drm_encoder_slave is not used in this file.
Signed-off-by: John Keeping
---
drivers/gpu/drm/rockchip/dw_hdmi-rockchip.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpu/drm/rockchip/dw_hdmi-rockchip.c
b/drivers/gpu/drm/rockchip/dw_hdmi-rockchip.c
index 801110f65a63..0665fb915579 1
Hi,
On Tue, 2016-05-10 at 07:29 -0700, Eric Dumazet wrote:
> On Tue, 2016-05-10 at 16:11 +0200, Paolo Abeni wrote:
> > Currently, the softirq loop can be scheduled both inside the ksofirqd kernel
> > thread and inside any running process. This makes nearly impossible for the
> > process scheduler
On Tue, May 10, 2016 at 01:04:41PM +0200, Borislav Petkov wrote:
> On Mon, May 09, 2016 at 01:45:58PM -0700, Yu-cheng Yu wrote:
> > If "xsaves" is enabled, kernel always uses compacted format of xsave area.
> > But user space still uses standard format of xsave area. Thus, xstate size
> > in kernel
The first patch wasn't found by sparse, but is something I noticed while
in the area. The following two fix all of the sparse warnings inside
drm/rockchip.
John Keeping (3):
drm/rockchip: dw_hdmi: remove unused #include
drm/rockchip: fb: add missing header
drm/rockchip: fix "should it be st
On 05/10/2016 11:11 AM, Ross Lagerwall wrote:
> Commit ff1e22e7a638 ("xen/events: Mask a moving irq") open-coded
> irq_move_irq() but left out checking if the IRQ is disabled. This broke
> resuming from suspend since it tries to move a (disabled) irq without
> holding the IRQ's desc->lock. Fix it b
On Tue, 2016-05-10 at 21:29 +0530, Vinod Koul wrote:
> On Wed, May 04, 2016 at 10:29:40PM +0300, Andy Shevchenko wrote:
> >
> > Rename cmd_pause to cmd_suspend to be clear that latter capability
> > reflects
> > pause AND resume.
> How does cmd_suspend be any clearer to reflect that channel is pau
On Tue, 10 May 2016, Paolo Abeni wrote:
Nice patch set and very promising results!
> At this point we are not really sure if we should go with this simpler
> approach by putting NAPI itself into kthreads or leverage the threadirqs
> function by putting the whole interrupt into a thread and signa
On 05/09/2016 09:29 PM, Jassi Brar wrote:
On Tue, May 10, 2016 at 5:15 AM, Stephen Warren wrote:
Jassi,
Does the HW described below sound like something that should be represented
using the Linux kernel's mailbox subsystem, and related DT bindings? I think
the existing drivers/mailbox/pcc.c is
(again, but not HTML)
On Tue, May 10, 2016 at 3:19 AM, Shawn Lin wrote:
> 在 2016/5/10 0:31, Doug Anderson 写道:
>>
>> Hi,
>>
>> On Mon, May 9, 2016 at 4:12 AM, Shawn Lin
>> wrote:
1. Specifying a single number for this property in terms of "degrees"
is probably not right. The whole
On Tue, May 10, 2016 at 12:37 PM, Benjamin Tissoires
wrote:
> @@ -92,7 +93,7 @@ soc_button_device_create(struct platform_device *pdev,
> continue;
>
> gpio = soc_button_lookup_gpio(&pdev->dev, info->acpi_index);
> - if (gpio < 0)
> +
On Wed, May 04, 2016 at 10:29:40PM +0300, Andy Shevchenko wrote:
> Rename cmd_pause to cmd_suspend to be clear that latter capability reflects
> pause AND resume.
How does cmd_suspend be any clearer to reflect that channel is paused and
not. One can argue this might be related to power management
Shaohua Li writes:
> if trace isn't enabled, parsing cgroup path just wastes cpu
>
> Signed-off-by: Shaohua Li
> ---
> block/blk-throttle.c | 5 ++---
> include/linux/blktrace_api.h | 9 +
> 2 files changed, 11 insertions(+), 3 deletions(-)
>
> diff --git a/block/blk-throttle.c
Fixed following checkpatch.pl warnings
WARNING: Prefer WRITE_ONCE(, ) over ACCESS_ONCE() =
WARNING: Prefer READ_ONCE() over ACCESS_ONCE()
Signed-off-by: Shyam Saini
---
drivers/staging/comedi/comedi_fops.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers
rk_iommu_command() takes a struct rk_iommu and iterates over the slave
MMUs, so this is doubly wrong in that we're passing in the wrong pointer
and talking to MMUs that we shouldn't be.
Fixes: cd6438c5f844 ("iommu/rockchip: Reconstruct to support multi slaves")
Signed-off-by: John Keeping
---
dr
From: Eric Dumazet
Date: Tue, 10 May 2016 07:29:50 -0700
> We already have ksoftirqd to normally cope with the case you are
> describing.
>
> If it is not working as intended, please identify the bugs and fix them,
> instead of adding yet another tests in fast path and extra complexity in
> the
On Wed, May 04, 2016 at 10:29:39PM +0300, Andy Shevchenko wrote:
> When check for capabilities recognize slave support by eother DMA_SLAVE or
^^^
typo
> DMA_CYCLIC bit set. If we don't do that the user can't get a normally worked
> DMA su
On Mon 09 May 17:36 PDT 2016, Andrew Duggan wrote:
> Hi Bjorn,
>
> On 05/06/2016 09:40 PM, Bjorn Andersson wrote:
> >The first version of the regulator support patch suffered from being
> >implemented in the transport driver, as a work around for resource
> >availability
> >racing (EPROBE_DEFER
On Mon, May 09, 2016 at 06:46:02PM -0400, Phillip Susi wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> It seems that mount --move does not work on a shared namespace ( now
> the default under systemd ), yet you can mount --bind and then umount
> the original, which seems to amount t
On Tue, 10 May 2016 09:52:41 -0500
Rob Herring wrote:
> On Tue, May 10, 2016 at 8:08 AM, Jean-Jacques Hiblot
> wrote:
> > 2016-05-10 14:41 GMT+02:00 Boris Brezillon
> > :
> >> On Tue, 10 May 2016 12:07:42 +0100
> >> Mark Rutland wrote:
> >>
> >>> On Tue, May 10, 2016 at 10:04:48AM +0200, B
On Tuesday 10 May 2016 17:14:37 Michal Marek wrote:
> On Mon, Apr 25, 2016 at 05:35:26PM +0200, Arnd Bergmann wrote:
> > Hi Michal,
> >
> > This is a resend of a series I originally sent back in February, but
> > unfortunately I never heard back from you. Could you apply these
> > patches for v4.7
Shaohua Li writes:
> BLK_TC_NOTIFY is missed in mask_maps, so we can't print out notify or
> set mask with 'notify' name.
For the text-based interface, yeah.
Reviewed-by: Jeff Moyer
>
> Signed-off-by: Shaohua Li
> ---
> kernel/trace/blktrace.c | 1 +
> 1 file changed, 1 insertion(+)
>
> dif
On Thu, May 05, 2016 at 10:42:12AM -0400, Christopher Covington wrote:
> On 03/31/2016 01:31 PM, Azriel Samson wrote:
> > The kernel headers package (linux-headers) doesn't include
> > header files from other architectures required to build
> > out-of-tree modules.
> >
> > For e.g. on ARM64, opcod
gpio_keys will later use gpio_is_valid(). To match the actual
behavior, we should use it here too.
Signed-off-by: Benjamin Tissoires
---
drivers/input/misc/soc_button_array.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/input/misc/soc_button_array.c
b/drivers/in
On 04/05/2016 21:09, Suravee Suthikulpanit wrote:
> From: Suravee Suthikulpanit
>
> When a vcpu is loaded/unloaded to a physical core, we need to update
> host physical APIC ID information in the Physical APIC-ID table
> accordingly.
>
> Also, when vCPU is blocking/un-blocking (due to halt ins
On Wed, May 04, 2016 at 03:35:39PM +0200, Bjørn Mork wrote:
> "objtool" is required for building external m dules if "Compile-time
> stack metadata validation" is enabled. Otherwise all builds based
> on the headers package fail with:
>
> make[1]: Entering directory '/usr/src/linux-headers-4.6.0
On Tue, May 10, 2016 at 6:23 PM, Andy Lutomirski wrote:
> Anyway, what kernel are you on? I think I fixed your specific issue in:
>
> commit 27747f8bc355a2808ca9e490ab6866acd85b4c16
> Author: Andy Lutomirski
> Date: Thu Jul 30 20:32:42 2015 -0700
>
> perf/x86/hw_breakpoints: Fix check for
From: Lars Ellenberg
Date: Tue, 10 May 2016 11:40:23 +0200
> If we introduce a new config option,
> we have to add it to the config scanner (one line),
> define min, max, default and scale (four short defines),
> and add it to the netlink definition here (one line).
> Done, rest of the code is ge
2016-03-15 13:10 GMT+03:00 Alexander Potapenko :
>
> static inline int kasan_module_alloc(void *addr, size_t size) { return 0; }
> static inline void kasan_free_shadow(const struct vm_struct *vm) {}
> diff --git a/lib/test_kasan.c b/lib/test_kasan.c
> index 82169fb..799c98e 100644
> --- a/lib/te
Hi,
This series has been triggered by the Surface 3 I have been given.
The way Microsoft follows its own specs is always intriguing. As
written in drivers/platform/x86/surfacepro3_button.c, the PNP0C40
ACPI device which should follow the specification doesn't have any
GPIO listed (thus the first 2
The Surface 3 declares twice the GPIO as GpioInt and GpioIo in its
ACPI table. Given that we do not keep the gpiod around, but the actual
number associated to, there is a chance while enumerating the GPIOs that
one gets assigned twice. Make sure a previous button has not been mapped
already to the
The PNP0C40 device of the Surface 3 doesn't have any GPIO attached to it.
Instead of trying to access the GPIO, request the count beforehand and
bail out if it is null or if an error is returned.
Signed-off-by: Benjamin Tissoires
---
drivers/input/misc/soc_button_array.c | 5 +
1 file change
Hi Alex,
On 05/10/2016 05:29 PM, Alex Williamson wrote:
> On Wed, 4 May 2016 11:54:15 +
> Eric Auger wrote:
>
>> The user is allowed to register a reserved MSI IOVA range by using the
>> DMA MAP API and setting the new flag: VFIO_DMA_MAP_FLAG_MSI_RESERVED_IOVA.
>> This region is stored in th
On 2016-05-03 03:22 PM, Eric Anholt wrote:
robert.f...@collabora.com writes:
From: Robert Foss
As per the documentation in drm_crtc.h, atomic_commit should return
-EBUSY if an asycnhronous update is requested and there is an earlier
update pending.
Note: docs cited here are drm_crtc.h, and
On Wed, 4 May 2016 11:54:15 +
Eric Auger wrote:
> The user is allowed to register a reserved MSI IOVA range by using the
> DMA MAP API and setting the new flag: VFIO_DMA_MAP_FLAG_MSI_RESERVED_IOVA.
> This region is stored in the vfio_dma rb tree. At that point the iova
> range is not mapped
When setting the IRQ type we don't check the return value to see if it
is set correctly. Due to this, failures to set the IRQ type have gone
unnoticed and because these failures were not catastrophic have not had
an impact on the system.
Ideally, we should return an error if we fail to set the typ
On Tue, May 03, 2016 at 10:04:03PM +0200, Miklos Szeredi wrote:
> Hi Al,
> git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs.git
> overlayfs-next
>
> This fixes two issues with overlayfs.
>
> Thanks,
> Miklos
>
> ---
> Miklos Szeredi (3):
> vfs: rename: check backing inode bein
In the function, setup_irq(), we don't check that the descriptor
returned from irq_to_desc() is valid before we start using it. For
example chip_bus_lock() called from setup_irq(), assumes that the
descriptor pointer is valid and doesn't check before dereferencing it.
In many other functions inclu
If the interrupt configuration matches the current configuration, then
don't bother writing the configuration again.
Signed-off-by: Jon Hunter
Acked-by: Marc Zyngier
---
drivers/irqchip/irq-gic-common.c | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/drivers/irqchip/
Most of these patches were originally part of the series to add support
for the Tegra210 AGIC [0]. However, given that series has grown and some
of the changes to the IRQ core needed some more review/testing, per an
offline discussion with Marc Z, I have split out the more trivial fixes
and clean-u
The firmware parameter that contains the IRQ sense bits may also contain
other data. When return the IRQ type, bits outside of these sense bits
should be masked. If these bits are not masked and
irq_create_fwspec_mapping() is called to map an IRQ, then the comparison
of the type returned from irq_d
On Tue, 2016-05-10 at 09:49 +0200, Mike Galbraith wrote:
> Only whacking
> cfs_rq_runnable_load_avg() with a rock makes schbench -m -t
> -a work well. 'Course a rock in its gearbox also
> rendered load balancing fairly busted for the general case :)
Smaller rock doesn't injure heavy tbench, b
If we fail to map the address space for the GIC distributor or CPU
interface, then don't attempt to initialise the chip, just WARN and
return.
Signed-off-by: Jon Hunter
Acked-by: Marc Zyngier
---
drivers/irqchip/irq-gic.c | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git
From: Masami Hiramatsu
Rewrite strbuf implementation not to use die() nor xrealloc(). Instead
of die(), now most of the API returns error code or 0 if succeeded.
Suggested-by: Arnaldo Carvalho de Melo
Signed-off-by: Masami Hiramatsu
Cc: Namhyung Kim
Cc: Peter Zijlstra
Link: http://lkml.kern
On Tue, May 10, 2016 at 4:50 AM, Ruslan Kabatsayev
wrote:
> On Tue, May 10, 2016 at 6:33 AM, Andy Lutomirski wrote:
>> Is there any reason at all for TASK_SIZE to be different from TASK_SIZE_MAX?
>
> The distinction originally appears to have been introduced by commit 8492980.
Hmm.
Anyway, what
From: Andi Kleen
Scale values by unit before passing them to the metrics printing
functions. This is needed for TopDown, because it needs to scale the
slots correctly by pipeline width / SMTness.
For existing metrics it shouldn't make any difference, as those
generally use events that don't hav
On 05/10/2016 08:53 AM, Namhyung Kim wrote:
> Currently ftracetest assumes tracing directory is located under
> $DEBUGFS/tracing. But it's possible to mount tracefs directly without
> debugfs.
>
> Signed-off-by: Namhyung Kim
Looks good to me. Steve! Ack if you are good with this patch.
I can ge
Setting the interrupt type for private peripheral interrupts (PPIs) may
not be supported by a given GIC because it is IMPLEMENTATION DEFINED
whether this is allowed. There is no way to know if setting the type is
supported for a given GIC and so the value written is read back to
verify it matches t
From: Masami Hiramatsu
Make pmu_formats_string() to check return value of strbuf APIs so that
it can detect errors in it.
Signed-off-by: Masami Hiramatsu
Cc: Namhyung Kim
Cc: Peter Zijlstra
Link: http://lkml.kernel.org/r/20160510054744.6158.37810.stgit@devbox
Signed-off-by: Arnaldo Carvalho d
On 05/10/2016 08:53 AM, Namhyung Kim wrote:
> Check event is filtered by set_event_pid and options/event-fork.
>
> Signed-off-by: Namhyung Kim
Looks good to me. Steve! Ack if you are good with this patch.
I can get this into 4.8-rc1
thanks,
-- Shuah
> ---
> .../selftests/ftrace/test.d/event/e
From: Jayachandran C
Add config option PCI_ECAM and file drivers/pci/ecam.c to provide
generic functions for accessing memory mapped PCI config space.
The API is defined in drivers/pci/ecam.h and is written to replace the
API in drivers/pci/host/pci-host-common.h. The file defines a new
'struct
From: Chris Phlipot
This change introduces a fix to symbols__find, so that it is able to
find symbols of length zero (where start == end).
The current code has the following problem:
- The current implementation of symbols__find is unable to find any symbols
of length zero.
- The db-export f
It is perfectly fine to use ACPI_PCI_HOST_GENERIC for ARM64,
so lets get rid of PCI init and RAW ACPI accessor empty stubs
and go with full-blown PCI host controller driver.
Signed-off-by: Tomasz Nowicki
To: Catalin Marinas
To: Lorenzo Pieralisi
To: Will Deacon
To: Arnd Bergmann
---
arch/arm
This patch provides a way to set the ACPI domain number in PCI code.
pci_create_root_bus is called with NULL as parent in ACPI. This
ends up calling pci_bus_assign_domain_nr with a NULL parent.
So we define acpi_pci_bus_domain_nr() which is meant to retrieve
the PCI domain number based on 'struct p
This patch provides a way to set the ACPI companion in PCI code.
We define acpi_pci_set_companion() to set the ACPI companion pointer and
call it from PCI core code. The function is stub for now.
Signed-off-by: Jayachandran C
Signed-off-by: Tomasz Nowicki
---
drivers/pci/probe.c | 2 ++
in
It is very useful to release I/O resources so that the same I/O resources
can be allocated again (pci_remap_iospace), like in PCI hotplug removal
scenario. Therefore this patch implements new pci_unmap_iospace call which
unmaps I/O space as the symmetry to pci_remap_iospace.
Signed-off-by: Sinan K
To enable PCI legacy IRQs on platforms booting with ACPI, arch code
should include ACPI specific callbacks that parse and set-up the
device IRQ number, equivalent to the DT boot path. Owing to the current
ACPI core scan handlers implementation, ACPI PCI legacy IRQs bindings
cannot be parsed at devi
No functional changes in this patch.
PCI I/O space mapping code does not depend on OF, therefore it can be
moved to PCI core code. This way we will be able to use it
e.g. in ACPI PCI code.
Suggested-by: Lorenzo Pieralisi
Signed-off-by: Tomasz Nowicki
CC: Arnd Bergmann
CC: Liviu Dudau
---
dri
401 - 500 of 988 matches
Mail list logo
