On 10/26/2016 06:50 PM, Brian Boylston wrote:
> copy_from_iter_nocache() now uses nocache copies for all types of iovecs
> on x86, so the flush in arch_copy_from_iter_pmem() is no longer needed.
>
> Cc: Ross Zwisler
> Cc: Thomas Gleixner
> Cc: Ingo Molnar
> Cc: "H. Peter Anvin"
> Cc:
> Cc: Al
2016-10-14 20:21+0200, Paolo Bonzini:
> Calling apic_find_highest_irr results in IRR being scanned twice,
> once in vmx_sync_pir_from_irr and once in apic_search_irr. Change
> sync_pir_from_irr to do the RVI write and kvm_apic_update_irr to
> compute the new RVI on the fly.
>
> Signed-off-by: Pao
On Wed, Oct 26, 2016 at 4:57 AM, Arnd Bergmann wrote:
> The newly added drm_of_component_match_add helper is defined as
> 'static' in a header when CONFIG_OF is disabled, causing a warning
> each time the header is included:
>
> In file included from /git/arm-soc/drivers/gpu/drm/bridge/dw-hdmi.c:2
On 10/26/2016 03:06 PM, Linus Torvalds wrote:
> On Wed, Oct 26, 2016 at 11:42 AM, Dave Jones wrote:
>>
>> The stacks show nearly all of them are stuck in sync_inodes_sb
>
> That's just wb_wait_for_completion(), and it means that some IO isn't
> completing.
>
> There's also a lot of processes w
On 10/26/2016 02:49 PM, ahas...@baylibre.com wrote:
From: Axel Haslam
The usb20_phy clock needs to be registered for the driver to be able
to get and enable a clock. Currently the usb phy clocks are registered
form board files, which will not be called during a device tree based
boot.
To be ab
On 27 September 2016 at 07:44, Suzuki K Poulose wrote:
> The mode of operation of the TMC tracked in drvdata->mode is defined
> as a local_t type. This is always checked and modified under the
> drvdata->spinlock and hence we don't need local_t for it and the
> unnecessary synchronisation instruct
On 10/26/2016 03:01 PM, David Lechner wrote:
On 10/26/2016 02:49 PM, ahas...@baylibre.com wrote:
From: Axel Haslam
The usb20_phy clock needs to be registered for the driver to be able
to get and enable a clock. Currently the usb phy clocks are registered
form board files, which will not be cal
On Wed, 26 Oct 2016, Yazen Ghannam wrote:
> Fix an underflow bug with the current Fam17h LLC ID derivation by
> simplifying the derivation, and also move it into amd_get_topology().
This changelog is useless.
It does not give any information what the bug is and what kind of damage it
does on whi
On 26/10/2016 21:01, Jann Horn wrote:
> On Wed, Oct 26, 2016 at 08:56:39AM +0200, Mickaël Salaün wrote:
>> This new arraymap looks like a set and brings new properties:
>> * strong typing of entries: the eBPF functions get the array type of
>> elements instead of CONST_PTR_TO_MAP (e.g.
>> CON
2016-10-14 20:21+0200, Paolo Bonzini:
> Since bf9f6ac8d749 ("KVM: Update Posted-Interrupts Descriptor when vCPU
> is blocked", 2015-09-18) the posted interrupt descriptor is checked
> unconditionally for PIR.ON. Therefore we don't need KVM_REQ_EVENT to
> trigger the scan and, if NMIs or SMIs are n
Hello, Daniel.
On Wed, Oct 26, 2016 at 09:25:25PM +0200, Daniel Vetter wrote:
> > > + * Note that callers must ensure that concurrent access to @ida is not
> > > possible.
> > > + * When simplicity trumps concurrency needs look at ida_simple_get()
> > > instead.
> >
> > Maybe we can make it a b
On Wednesday 26 October 2016 02:17 AM, John Youn wrote:
> On 10/25/2016 7:15 AM, Randy Li wrote:
>> I forget to add a dummy function in case the CONFIG_GENERIC_PHY
>> is disabled.
>>
>> Signed-off-by: Randy Li
>
> Fixes: cac18ecb6f44 ("phy: Add reset callback")
> Tested-by: John Youn
>
> Hi K
Hi,
On Wednesday 19 October 2016 04:13 PM, Vivek Gautam wrote:
> Qualcomm SOCs have QMP phy controller that provides support
> to a number of controller, viz. PCIe, UFS, and USB.
> Add a new driver, based on generic phy framework, for this
> phy controller.
>
> USB3-phy changes: Based on phy-msm-
2016-10-14 20:21+0200, Paolo Bonzini:
> Pending interrupts might be in the PI descriptor when the
> LAPIC is restored from an external state; we do not want
> them to be injected.
>
> Signed-off-by: Paolo Bonzini
> ---
Reviewed-by: Radim Krčmář
wm97xx-core does several things in it initialization :
- touchscreen input device setup
- battery device creation
As the wm97xx is actually a multi-function device handling an audio
codec, a touchscreen, a gpio block and an ADC, reshape the probing to
isolate what is truly input/touchscreen spec
The WM9705, WM9712 and WM9713 are highly integrated codecs, with an
audio codec, DAC and ADC, GPIO unit and a touchscreen interface.
Historically the support was spread across drivers/input/touchscreen and
sound/soc/codecs. The sharing was done through ac97 bus sharing. This
model will not withsta
On Wed, Oct 26, 2016 at 10:03 PM, David Lechner wrote:
> On 10/26/2016 03:01 PM, David Lechner wrote:
>>
>> On 10/26/2016 02:49 PM, ahas...@baylibre.com wrote:
>>>
>>> From: Axel Haslam
>>>
>>> The usb20_phy clock needs to be registered for the driver to be able
>>> to get and enable a clock. Cur
Hello Sir/Madam,
You have been Chosen to benefit from Susanne Klatten 50M Philanthropic Donation.
Contact: charityanddonat...@aol.de
On 10/26/2016 03:05 PM, Axel Haslam wrote:
On Wed, Oct 26, 2016 at 10:03 PM, David Lechner wrote:
On 10/26/2016 03:01 PM, David Lechner wrote:
On 10/26/2016 02:49 PM, ahas...@baylibre.com wrote:
From: Axel Haslam
The usb20_phy clock needs to be registered for the driver to be able
to get
On Wed, Oct 26, 2016 at 10:03:09PM +0200, Mickaël Salaün wrote:
> On 26/10/2016 21:01, Jann Horn wrote:
> > On Wed, Oct 26, 2016 at 08:56:39AM +0200, Mickaël Salaün wrote:
> >> This new arraymap looks like a set and brings new properties:
> >> * strong typing of entries: the eBPF functions get the
On Wed, Oct 26, 2016 at 09:56:13AM -0400, Nicolas Pitre wrote:
> So if my Fedora usage doesn't need them, we can infer that
> the number of embedded systems also not needing them might tend towards
> a high percentage.
(I wouldn't call Fedora an embedded distro, but heh...)
> But let's be conse
Resubmition of arcxcnn backliught driver bindings with added register
documentation
Signed-off-by: Olimpiu Dejeu
---
.../bindings/leds/backlight/arcxcnn_bl.txt | 31 ++
1 file changed, 31 insertions(+)
create mode 100644
Documentation/devicetree/bindings/leds/back
Hi,
Maybe this is a stupid question and I didn't test this with SELinux, but
it looks to me that SELinux execmem does not prevent process from
getting writable and executable memory mappings by using shmat(...,
SHM_EXEC). Shouldn't this be blocked by execmem, I suppose it is there
to prevent this
On Wed, Oct 26, 2016 at 10:15:30AM -0700, Linus Torvalds wrote:
> On Wed, Oct 26, 2016 at 9:32 AM, Linus Torvalds
> wrote:
> >
> > Quite frankly, I think the solution is to just rip out all the insane
> > zone crap.
>
> IOW, something like the attached.
>
> Advantage:
>
> - just look at the nu
Resubmition of arcxcnn backliught driver adding devicetree entries
for all registers
Signed-off-by: Olimpiu Dejeu
---
drivers/video/backlight/Kconfig | 7 +
drivers/video/backlight/Makefile | 1 +
drivers/video/backlight/arcxcnn_bl.c | 541 +++
incl
2016-10-14 20:21+0200, Paolo Bonzini:
> Synchronizing PIR to IRR is not needed in most callers of
> apic_find_highest_irr. Move it to the one place that matters,
> interrupt acknowledgement.
>
> Signed-off-by: Paolo Bonzini
> ---
Reviewed-by: Radim Krčmář
> diff --git a/arch/x86/kvm/lapic.c b
On Tuesday 18 October 2016 07:58 PM, Vivek Gautam wrote:
> remove() callback does a phy_exit() only and nothing else now.
remove callback calls a phy_power_off() ;-)
-Kishon
> The phy_exit() over the generic phy is called from the phy
> consumer, and phy provider driver should not explicitly n
Hi
On Wed, Oct 26, 2016 at 9:39 PM, Linus Torvalds
wrote:
> So the thing that tends to worry me about these is resource management.
>
> If I understood the documentation correctly, this has per-user
> resource management, which guarantees that at least the system won't
> run out of memory. Good.
The rework of the PM support has caused two functions to
be orphaned when CONFIG_PM is disabled:
media/i2c/smiapp/smiapp-core.c:1352:12: error: 'smiapp_power_off' defined but
not used [-Werror=unused-function]
media/i2c/smiapp/smiapp-core.c:1206:12: error: 'smiapp_power_on' defined but
not used
On Wed, 26 Oct 2016 12:01:28 -0600
Alex Williamson wrote:
> Signed-off-by: Alex Williamson
> ---
> drivers/pci/pci.c | 29 +
> drivers/pci/pcie/aspm.c | 17 +
> include/linux/pci.h |1 +
> 3 files changed, 31 insertions(+), 16 deleti
On Sat, 22 Oct 2016, Fenghua Yu wrote:
> +config INTEL_RDT_A
> + bool "Intel Resource Director Technology Allocation support"
> + default n
> + depends on X86 && CPU_SUP_INTEL
depends on X86 is more than pointless for a config switch which sits in the
arch/x86/Kconfig file
Thanks,
I believe our trademark guidelines say we aren't supposed to use VMware as a
noun to mean a product, only to mean the company. So we can say "running on
VMware ESXi" or "running in a VMware virtual machine", but "running on VMware"
is wrong. There is supposedly some good legal reason for this rel
On Wed, 26 Oct 2016, Thomas Garnier wrote:
> Okay, I think for SLAB we can allow everything except the two flags
> mentioned here.
No no no. Just allow the flags already defined in include/linux/slab.h
that can be specd by subsystems when they call into the slab allocators.
> Should I deny certa
On Wed, 26 Oct 2016, Tim Mann wrote:
> I believe our trademark guidelines say we aren't supposed to use VMware as a
> noun to mean a product, only to mean the company. So we can say "running on
> VMware ESXi" or "running in a VMware virtual machine", but "running on VMware"
> is wrong. There is
Internal errors were reported on 16 bit fxsave and fxrstor with iPXE.
Old Intels don't have unrestricted_guest, so we have to emulate them.
The patch takes advantage of the hardware implementation. There should
be no problem as long as the buffer is aligned.
Signed-off-by: Radim Krčmář
---
I'
[1/2] adds the emulation (and could be split into two patches if you'd like),
[2/2] just refactors the code.
This should fix an issue that users are hitting. Laszlo found several reports:
- https://bugs.launchpad.net/qemu/+bug/1623276
- https://bugzilla.proxmox.com/show_bug.cgi?id=1182
- https
Alignments are exclusive, so 5 modes can be expressed in 3 bits.
Signed-off-by: Radim Krčmář
---
arch/x86/kvm/emulate.c | 23 +--
1 file changed, 13 insertions(+), 10 deletions(-)
diff --git a/arch/x86/kvm/emulate.c b/arch/x86/kvm/emulate.c
index f360876d6b7f..8fe2dbfb6338 1
Since the dawn of time, our background buffered writeback has sucked.
When we do background buffered writeback, it should have little impact
on foreground activity. That's the definition of background activity...
But for as long as I can remember, heavy buffered writers have not
behaved like that.
Enable throttling of buffered writeback to make it a lot
more smooth, and has way less impact on other system activity.
Background writeback should be, by definition, background
activity. The fact that we flush huge bundles of it at the time
means that it potentially has heavy impacts on foreground
This adds a new request flag, REQ_BG, that callers can use to tell
the block layer that this is background (non-urgent) IO.
Signed-off-by: Jens Axboe
---
include/linux/blk_types.h | 4 +++-
include/linux/fs.h| 3 +++
2 files changed, 6 insertions(+), 1 deletion(-)
diff --git a/include/l
We can hook this up to the block layer, to help throttle buffered
writes.
wbt registers a few trace points that can be used to track what is
happening in the system:
wbt_lat: 259:0: latency 2446318
wbt_stat: 259:0: rmean=2446318, rmin=2446318, rmax=2446318, rsamples=1,
wmean=518866
For legacy block, we simply track them in the request queue. For
blk-mq, we track them on a per-sw queue basis, which we can then
sum up through the hardware queues and finally to a per device
state.
The stats are tracked in, roughly, 0.1s interval windows.
Add sysfs files to display the stats.
If we're doing background type writes, then use the appropriate
write command for that.
Signed-off-by: Jens Axboe
---
include/linux/writeback.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/include/linux/writeback.h b/include/linux/writeback.h
index 78b87c517b5f..f12f0b34daca 100644
---
For blk-mq, ->nr_requests does track queue depth, at least at init
time. But for the older queue paths, it's simply a soft setting.
On top of that, it's generally larger than the hardware setting
on purpose, to allow backup of requests for merging.
Fill a hole in struct request with a 'queue_depth
Note in the bdi_writeback structure whenever a task ends up sleeping
waiting for progress. We can use that information in the lower layers
to increase the priority of writes.
Signed-off-by: Jens Axboe
---
include/linux/backing-dev-defs.h | 2 ++
mm/backing-dev.c | 1 +
mm/page-wr
Add wbc_to_write_flags(), which returns the write modifier flags to use,
based on a struct writeback_control. No functional changes in this
patch, but it prepares us for factoring other wbc fields for write type.
Signed-off-by: Jens Axboe
Reviewed-by: Jan Kara
---
fs/buffer.c | 2
Hi!
I'd like to get an interrupt every million cache misses... to do a
printk() or something like that. As far as I can tell, modern hardware
should allow me to do that. AFAICT performance events subsystem can do
something like that, but I can't figure out where the code is / what I
should call.
On Tue, Oct 25, 2016 at 12:24:24AM +0530, Kashyap Desai wrote:
> > -Original Message-
> > From: Omar Sandoval [mailto:osan...@osandov.com]
> > Sent: Monday, October 24, 2016 9:11 PM
> > To: Kashyap Desai
> > Cc: linux-s...@vger.kernel.org; linux-kernel@vger.kernel.org; linux-
> > bl...@vger
We have encountered some RMI4 firmwares where there are blank pages in
between PDT pages which contain functions. This change makes them
correctly enumerate all functions on the device.
Tested on S7817 (has empty page 2).
Signed-off-by: Nick Dyer
[Tested successfully on S7817 and S7300 Synaptics
On Wed, Oct 26, 2016 at 02:56:57PM +0200, Uwe Kleine-König wrote:
> It makes the result hard to interpret correctly if a base 10 number is
> prefixed by 0x. So change to a hex number.
>
Would like to have this be a decimal number.
Signed-off-by: Dimitri Sivanich
---
drivers/misc/sgi-gru/grumain
- Original Message -
| On Wed, Oct 26, 2016 at 11:04 AM, Bob Peterson wrote:
| >
| > I can test it for you, if you give me about an hour.
|
| I can definitely wait an hour, it would be lovely to see more testing.
| Especially if you have a NUMA machine and an interesting workload.
|
| An
On Tue, Oct 18, 2016 at 04:05:35PM -0500, Zach Brown wrote:
> On some systems the sdhci capabilty registers are incorrect for one
> reason or another.
>
> The sdhci-cap-speed-modes-broken property will let the driver know that
> the sdhci capability registers should not be relied on for speed mode
On Wed, Oct 19, 2016 at 12:44:44AM +0200, Clemens Gruber wrote:
> Support setting the reference voltage in the device tree.
> Rework of driver structure, put chip specific data in a separate
> structure and assign it depending on device id from platform data or
> DT match.
> Extend the device docum
From: Manjunath Goudar
Separate the Davinci OHCI host controller driver from ohci-hcd
host code so that it can be built as a separate driver module.
This work is part of enabling multi-platform kernels on ARM
Signed-off-by: Manjunath Goudar
[Axel: adapted and rebased, fixed minor comments]
Sign
--
Geschäftsvorschlag!!!
Ich vermute das diese E-Mail eine Überraschung für Sie sein wird, aber
es ist wahr.Ich bin bei einer routinen Überprüfung in meiner Bank (First
National Bank von Süd Afrika) wo ich arbeite, auf einem Konto gestoßen,
was nicht in anspruch genommen worden ist, wo derz
Hi Jay,
On Wed, Oct 26, 2016 at 8:00 PM, Jay Vosburgh
wrote:
> Philippe Reynes wrote:
>
>>The ethtool api {get|set}_settings is deprecated.
>>We move this driver to new api {get|set}_link_ksettings.
>
> This is just an API change, i.e., no change to functionality?
Yes, it's juste an API
On Wed, Oct 19, 2016 at 11:40:56AM +0200, Clemens Gruber wrote:
> Documents the devicetree bindings for the Microchip MCP3021/3221.
>
> Signed-off-by: Clemens Gruber
> ---
> Documentation/devicetree/bindings/hwmon/mcp3021.txt | 21
> +
> 1 file changed, 21 insertions(+)
> c
On Wed, Oct 26, 2016 at 03:02:56PM +0200, Thomas Gleixner wrote:
> On Sat, 22 Oct 2016, Fenghua Yu wrote:
> > +void rdt_cbm_update(void *arg)
> > +{
> > + struct msr_param *m = (struct msr_param *)arg;
> > + struct rdt_resource *r = m->res;
> > + int i, cpu = smp_processor_id();
> > + struc
On Wed, Oct 19, 2016 at 04:13:46PM +0530, Vivek Gautam wrote:
> PHY transceiver driver for QUSB2 phy controller that provides
> HighSpeed functionality for DWC3 controller present on
> Qualcomm chipsets.
>
> This driver is based on phy-msm-qusb driver available in
> msm-4.4 kernel @codeaurora[1]
>
From: Xo Wang
Date: Fri, 21 Oct 2016 10:20:11 -0700
> This series is based on tip of torvalds/master.
>
> The first patch adds register definitions from Broadcom docs.
>
> The second patch adds the BCM54612E PHY ID, flags, and device-specific
> RGMII internal delay initialization.
>
> I tested
On Wed, Oct 19, 2016 at 04:13:47PM +0530, Vivek Gautam wrote:
> Qualcomm SOCs have QMP phy controller that provides support
> to a number of controller, viz. PCIe, UFS, and USB.
> Add a new driver, based on generic phy framework, for this
> phy controller.
>
> USB3-phy changes: Based on phy-msm-ss
From: Sven Eckelmann
Date: Sat, 22 Oct 2016 09:46:24 +0200
> The maximum MTU is defined via the slave devices of an batman-adv
> interface. Thus it is not possible to calculate the max_mtu during the
> creation of the batman-adv device when no slave devices are attached. Doing
> so would for exam
On Wed, 26 Oct 2016, Fenghua Yu wrote:
> On Wed, Oct 26, 2016 at 03:02:56PM +0200, Thomas Gleixner wrote:
> > > + list_for_each(l, &r->domains) {
> > > + d = list_entry(l, struct rdt_domain, list);
> >
> > So above you converted to list_for_each_entry(). Is there a sensible
> > reason, asi
Commit-ID: e9a2ea5a1ba09c35258f3663842fb8d8cf2e00c2
Gitweb: http://git.kernel.org/tip/e9a2ea5a1ba09c35258f3663842fb8d8cf2e00c2
Author: Fenghua Yu
AuthorDate: Sat, 22 Oct 2016 06:19:49 -0700
Committer: Thomas Gleixner
CommitDate: Wed, 26 Oct 2016 23:12:37 +0200
cacheinfo: Introduce cach
Commit-ID: 1d78dc59f5ab6f467e49882518453adc7e4caa44
Gitweb: http://git.kernel.org/tip/1d78dc59f5ab6f467e49882518453adc7e4caa44
Author: Tony Luck
AuthorDate: Sat, 22 Oct 2016 06:19:48 -0700
Committer: Thomas Gleixner
CommitDate: Wed, 26 Oct 2016 23:12:37 +0200
Documentation, ABI: Docume
Commit-ID: d57e3ab7e34c51a8badeea1b500bfb738d0af66e
Gitweb: http://git.kernel.org/tip/d57e3ab7e34c51a8badeea1b500bfb738d0af66e
Author: Fenghua Yu
AuthorDate: Sat, 22 Oct 2016 06:19:50 -0700
Committer: Thomas Gleixner
CommitDate: Wed, 26 Oct 2016 23:12:37 +0200
x86/intel_cacheinfo: Enab
On Wed, Oct 26, 2016 at 1:31 PM, Mel Gorman wrote:
>
> IO wait activity is not all that matters. We hit the lock/unlock paths
> during a lot of operations like reclaim.
I doubt we do.
Yes, we hit the lock/unlock itself, but do we hit the *contention*?
The current code is nasty, and always ends
Commit-ID: 4ab1586488cb56ed8728e54c4157cc38646874d9
Gitweb: http://git.kernel.org/tip/4ab1586488cb56ed8728e54c4157cc38646874d9
Author: Fenghua Yu
AuthorDate: Sat, 22 Oct 2016 06:19:51 -0700
Committer: Thomas Gleixner
CommitDate: Wed, 26 Oct 2016 23:12:38 +0200
x86/cpufeature: Add RDT C
This series adds Mediated device support to Linux host kernel. Purpose
of this series is to provide a common interface for mediated device
management that can be used by different devices. This series introduces
Mdev core module that creates and manages mediated devices, VFIO based
driver for media
Commit-ID: 113c60970cf41723891e3a1b303517eaf8510bb5
Gitweb: http://git.kernel.org/tip/113c60970cf41723891e3a1b303517eaf8510bb5
Author: Fenghua Yu
AuthorDate: Sat, 22 Oct 2016 06:19:54 -0700
Committer: Thomas Gleixner
CommitDate: Wed, 26 Oct 2016 23:12:38 +0200
x86/intel_rdt: Add Haswel
Design for Mediated Device Driver:
Main purpose of this driver is to provide a common interface for mediated
device management that can be used by different drivers of different
devices.
This module provides a generic interface to create the device, add it to
mediated bus, add device to IOMMU grou
Add find_iommu_group()
Signed-off-by: Kirti Wankhede
Signed-off-by: Neo Jia
Change-Id: I9d372f1ebe9eb01a5a21374b8a2b03f7df73601f
---
drivers/vfio/vfio_iommu_type1.c | 58 -
1 file changed, 34 insertions(+), 24 deletions(-)
diff --git a/drivers/vfio/vfio_
This change rearrange functions to have common function to increment
container_users
Signed-off-by: Kirti Wankhede
Signed-off-by: Neo Jia
Change-Id: I8bdeb352bc8439b107ffd519480fd4dc238677f2
---
drivers/vfio/vfio.c | 34 +-
1 file changed, 21 insertions(+), 13 de
On Wed, Oct 26, 2016 at 2:01 PM, Bob Peterson wrote:
>
> Hm. It didn't even boot, at least on my amd box in the lab.
> I've made no attempt to debug this.
Hmm. Looks like a completely independent issue from the patch. Did you
try booting that machine without the patch?
> [2.378877] kernel BU
Update arguments of vaddr_get_pfn() to take struct mm_struct *mm as input
argument.
Signed-off-by: Kirti Wankhede
Signed-off-by: Neo Jia
Change-Id: I885fd4cd4a9f66f4ee2c1caf58267464ec239f52
---
drivers/vfio/vfio_iommu_type1.c | 25 ++---
1 file changed, 18 insertions(+), 7 d
Commit-ID: 78e99b4a2b9afb1c304259fcd4a1c71ca97e3acd
Gitweb: http://git.kernel.org/tip/78e99b4a2b9afb1c304259fcd4a1c71ca97e3acd
Author: Fenghua Yu
AuthorDate: Sat, 22 Oct 2016 06:19:53 -0700
Committer: Thomas Gleixner
CommitDate: Wed, 26 Oct 2016 23:12:38 +0200
x86/intel_rdt: Add CONFIG
From: Stefan Richter
Date: Sun, 23 Oct 2016 16:29:03 +0200
> Commit b3e3893e1253 ("net: use core MTU range checking in misc drivers")
> mistakenly introduced an upper limit for firewire-net's MTU based on the
> local link layer controller's reception capability. Revert this. Neither
> RFC 2734
2016-10-26 Brian Starkey :
> Some parts of setting up the CRTC out-fence can be re-used for
> writeback out-fences. Factor this out into a separate function.
>
> Signed-off-by: Brian Starkey
> ---
> drivers/gpu/drm/drm_atomic.c | 64
> +++---
> 1 file chan
Vendor driver using mediated device framework would use same mechnism to
validate and prepare IRQs. Introducing this function to reduce code
replication in multiple drivers.
Signed-off-by: Kirti Wankhede
Signed-off-by: Neo Jia
Change-Id: Ie201f269dda0713ca18a07dc4852500bd8b48309
---
drivers/vfi
The Sample driver creates mdev device that simulates serial port over PCI
card.
Signed-off-by: Kirti Wankhede
Signed-off-by: Neo Jia
Change-Id: I857f8f12f8b275f2498dfe8c628a5cdc7193b1b2
---
Documentation/vfio-mdev/Makefile | 13 +
Documentation/vfio-mdev/mtty.c
Added details of sysfs ABI for mediated device framework
Signed-off-by: Kirti Wankhede
Signed-off-by: Neo Jia
Change-Id: Icb0fd4ed58a2fa793fbcb1c3d5009a4403c1f3ac
---
Documentation/ABI/testing/sysfs-bus-vfio-mdev | 111 ++
1 file changed, 111 insertions(+)
create mode 1
Added two new callback functions to struct vfio_iommu_driver_ops. Backend
IOMMU module that supports pining and unpinning pages for mdev devices
should provide these functions.
Added APIs for pining and unpining pages to VFIO module. These calls back
into backend iommu module to actually pin and un
Defined device API strings. Vendor driver using mediated device
framework should use corresponding string for device_api attribute.
Signed-off-by: Kirti Wankhede
Signed-off-by: Neo Jia
Change-Id: I42d29f475f02a7132ce13297fbf2b48f1da10995
---
include/uapi/linux/vfio.h | 10 ++
1 file cha
Commit-ID: 6b281569df649ed76145c527028fbbe8a32493aa
Gitweb: http://git.kernel.org/tip/6b281569df649ed76145c527028fbbe8a32493aa
Author: Fenghua Yu
AuthorDate: Sat, 22 Oct 2016 06:19:56 -0700
Committer: Thomas Gleixner
CommitDate: Wed, 26 Oct 2016 23:12:39 +0200
x86/cqm: Share PQR_ASSOC
Add file Documentation/vfio-mediated-device.txt that include details of
mediated device framework.
Signed-off-by: Kirti Wankhede
Signed-off-by: Neo Jia
Change-Id: I137dd646442936090d92008b115908b7b2c7bc5d
---
Documentation/vfio-mdev/vfio-mediated-device.txt | 297 +++
1 file
From: Stefan Richter
Date: Sun, 23 Oct 2016 16:30:56 +0200
> firewire-net, like the older eth1394 driver, reduced the initial MTU to
> less than 1500 octets if the local link layer controller's asynchronous
> packet reception limit was lower.
>
> This is bogus, since this reception limit does no
Added blocking notifier to IOMMU TYPE1 driver to notify vendor drivers
about DMA_UNMAP.
Exported two APIs vfio_register_notifier() and vfio_unregister_notifier().
Vendor driver should register notifer using these APIs.
Vendor driver should use VFIO_IOMMU_NOTIFY_DMA_UNMAP action to invalidate
mappin
Update msix_sparse_mmap_cap() to use vfio_info_add_capability()
Update region type capability to use vfio_info_add_capability()
Signed-off-by: Kirti Wankhede
Signed-off-by: Neo Jia
Change-Id: I52bb28c7875a6da5a79ddad1843e6088aff58a45
---
drivers/vfio/pci/vfio_pci.c | 49 ++--
Commit-ID: c1c7c3f9d6bb6999a45f66ea4c6bfbcab87ff34b
Gitweb: http://git.kernel.org/tip/c1c7c3f9d6bb6999a45f66ea4c6bfbcab87ff34b
Author: Fenghua Yu
AuthorDate: Sat, 22 Oct 2016 06:19:55 -0700
Committer: Thomas Gleixner
CommitDate: Wed, 26 Oct 2016 23:12:39 +0200
x86/intel_rdt: Pick up L3
On 10/26/2016 06:43 AM, Robert Richter wrote:
On 25.10.16 14:31:00, David Daney wrote:
From: David Daney
On arm64 NUMA kernels we can pass "numa=off" on the command line to
disable NUMA. A side effect of this is that kmalloc_node() calls to
non-zero nodes will crash the system with an OOPS:
Updated vfio_platform_common.c file to use
vfio_set_irqs_validate_and_prepare()
Signed-off-by: Kirti Wankhede
Signed-off-by: Neo Jia
Change-Id: Id87cd6b78ae901610b39bf957974baa6f40cd7b0
---
drivers/vfio/platform/vfio_platform_common.c | 31 +++-
1 file changed, 8 inserti
Updated vfio_pci.c file to use vfio_set_irqs_validate_and_prepare()
Signed-off-by: Kirti Wankhede
Signed-off-by: Neo Jia
Change-Id: I9f3daba89d8dba5cb5b01a8cff420412f30686c7
---
drivers/vfio/pci/vfio_pci.c | 29 +
1 file changed, 9 insertions(+), 20 deletions(-)
dif
On Mon, Oct 24, 2016 at 01:38:54PM +, Tirdea, Irina wrote:
> > On Thu, Oct 20, 2016 at 11:52:38PM +0200, Thomas Gleixner wrote:
> > > On Mon, 17 Oct 2016, Irina Tirdea wrote:
> > > > The patch has already been reviewed by Stephen Boyd [1].
> > > > The only remaining question is the one pointed
VFIO IOMMU drivers are designed for the devices which are IOMMU capable.
Mediated device only uses IOMMU APIs, the underlying hardware can be
managed by an IOMMU domain.
Aim of this change is:
- To use most of the code of TYPE1 IOMMU driver for mediated devices
- To support direct assigned device
Vendor driver using mediated device framework should use
vfio_info_add_capability() to add capabilities.
Introduced this function to reduce code duplication in vendor drivers.
Signed-off-by: Kirti Wankhede
Signed-off-by: Neo Jia
Change-Id: I6fca329fa2291f37a2c859d0bc97574d9e2ce1a6
---
drivers/v
Updated arguments of vfio_lock_acct to take task as input argument
Signed-off-by: Kirti Wankhede
Signed-off-by: Neo Jia
Change-Id: I5d3673cc9d3786bb436b395d5f74537f1a36da80
---
drivers/vfio/vfio_iommu_type1.c | 20 ++--
1 file changed, 10 insertions(+), 10 deletions(-)
diff --g
This patch rearranges functions to get vfio_group from device
Signed-off-by: Kirti Wankhede
Signed-off-by: Neo Jia
Change-Id: I1f93262bdbab75094bc24b087b29da35ba70c4c6
---
drivers/vfio/vfio.c | 23 ---
1 file changed, 16 insertions(+), 7 deletions(-)
diff --git a/drivers/vf
vfio_mdev driver registers with mdev core driver.
mdev core driver creates mediated device and calls probe routine of
vfio_mdev driver for each device.
Probe routine of vfio_mdev driver adds mediated device to VFIO core module
This driver forms a shim layer that pass through VFIO devices operation
2016-10-26 Brian Starkey :
> Add the OUT_FENCE_PTR property to writeback connectors, to enable
> userspace to get a fence which will signal once the writeback is
> complete.
>
> A timeline is added to drm_connector for use by the writeback
> out-fences. It is up to drivers to check for a fence in
On 10/26/16 22:50, Radim Krčmář wrote:
> [1/2] adds the emulation (and could be split into two patches if you'd like),
> [2/2] just refactors the code.
>
> This should fix an issue that users are hitting. Laszlo found several
> reports:
> - https://bugs.launchpad.net/qemu/+bug/1623276
> - http
101 - 200 of 1294 matches
Mail list logo
