Introduces ioctl access to the VFIO AP Matrix device driver
by implementing the VFIO_DEVICE_GET_INFO ioctl. This ioctl
provides the VFIO AP Matrix device driver information to the
guest machine.
Signed-off-by: Tony Krowiak
---
drivers/s390/crypto/vfio_ap_matrix_ops.c | 43 +
Each adapter assigned to the mediated matrix device
must be validated to ensure that the adapter is accessible
from one of the AP queues bound to the AP matrix device
driver. Each AP queue bound to the matrix device is
identified by its AP Queue Number (APQN). An APQN is
comprised of an adapter ID
Overview:
An adjunct processor (AP) facility is an IBM Z cryptographic facility. The
AP facility is comprised of three AP instructions and from 1 to 256 AP
adapter cards. The design takes advantage of the interpretive execution mode
provided by the SIE architecture. With interpretive ex
Registers a group notifier during the open of the mediated
device to get information on KVM presence through the
VFIO_GROUP_NOTIFY_SET_KVM event.
When notified, save the pointer to KVM inside mediated matrix device
structure.
Signed-off-by: Tony Krowiak
---
drivers/s390/crypto/vfio_ap_matrix_op
The Crypto Control Block (CRYCB) is referenced by the SIE state
description and controls KVM guest access to the Adjunct
Processor (AP) adapters, usage domains and control domains.
This patch defines the AP control blocks to be used for
controlling guest access to the AP adapters and domains.
Sign
Introduces a new AP matrix device driver. This device driver
will ultimately perform the following functions:
* Register with the AP bus to let it know that the matrix
driver can control AP queue devices. This will allow
an administrator to unbind an AP queue device from its
device driver an
Introduces an AP matrix bus. The sysfs location of the
AP matrix bus is:
/sys/bus/ap_matrix
The AP matrix bus will create an AP matrix device that will
hold the AP queues reserved for use by KVM guests.
Signed-off-by: Tony Krowiak
---
MAINTAINERS |8 +
drivers/s
> So instead of adding helpers the 1<< ops can be written out explicitly - they
> are
> easy to read after all. Can also be:
>
> var &= ~BIT(bit);
> var |= BIT(bit);
It's some more complicated because "var" are arrays.
Opencoding is fairly ugly.
I changed the main bitmap to use DEC
Each domain assigned to the mediated matrix device
must be validated to ensure that the domain is accessible
from one of the AP queues bound to the AP matrix device
driver.
Each AP queue bound to the device driver is identified by
an AP Queue Number (APQN). An APQN is comprised of an
adapter ID (A
On Fri, Oct 13, 2017 at 10:01 AM, Al Viro wrote:
> On Fri, Oct 13, 2017 at 08:56:10AM -0700, Dan Williams wrote:
>> While implementing MAP_DIRECT, an mmap flag that arranges for an
>> FL_LAYOUT lease to be established, Al noted:
>>
>> You are not even guaranteed that descriptor will remain be
Registers the matrix device created by the AP matrix bus with
the VFIO mediated device framework. Registering the matrix
device will create the sysfs structures needed to create
mediated matrix devices that can be configured with a matrix
of adapters, usage domains and control domains for a guest
m
On Sat, 2017-10-14 at 01:29 +0800, Ming Lei wrote:
> ->can_queue is size of the whole tag space shared by all LUNs, looks it isn't
> reasonable to increase cmd_per_lun to .can_queue.
Sorry but I disagree. Setting cmd_per_lun to a value lower than can_queue
will result in suboptimal performance if
> -Original Message-
> From: Greg KH [mailto:g...@kroah.com]
> Sent: Friday, October 13, 2017 10:56 AM
> To: Limonciello, Mario
> Cc: dvh...@infradead.org; gno...@lxorguk.ukuu.org.uk;
> andy.shevche...@gmail.com; linux-kernel@vger.kernel.org; platform-driver-
> x...@vger.kernel.org; l...@k
This patch introduces the following changes to crypto initialization.
* For key management operations support, the crypto control block
(CRYCB) referenced by the KVM guest's SIE state description is
formatted only if the Message-Security-Assist (MSA) extension 3
facility is installed (STFLE.
Creates a single AP matrix device on the AP matrix bus.
The matrix device will be created as part of the AP matrix bus
initialization. The matrix device will hold the AP queues that
have been reserved for use by KVM guests. Mediated matrix devices
can then be created for each guest. The mediated ma
Provides the sysfs interfaces for assigning an AP usage domain
to and unassigning a usage domain from a mediated matrix device.
The relevant sysfs structures are:
/sys/devices/ap_matrix
... [matrix]
.. [mdev_supported_types]
. [ap_matrix-passthrough]
[devices]
...
This patch introduces a new compilation unit that will contain
all of the data structures and logic for configuring AP adapters,
usage domains and control domains for a KVM guest.
Signed-off-by: Tony Krowiak
---
MAINTAINERS |2 ++
arch/s390/include/asm/ap-config.h | 1
> > + /*
> > +* Clear XSAVE features that are disabled in the normal CPUID.
> > +*/
> > + for (i = 0; i < ARRAY_SIZE(xsave_cpuid_features); i++) {
> > + if (!boot_cpu_has(xsave_cpuid_features[i]))
> > + xfeatures_mask &= ~BIT(i);
> > + }
> > +
> > xfeat
Hi,
On 10/13/2017 04:53 AM, Hanjun Guo wrote:
Hi Jeremy,
On 2017/10/13 3:48, Jeremy Linton wrote:
Now that we have a PPTT parser, in preparation for its use
on arm64, lets build it.
Signed-off-by: Jeremy Linton
---
arch/arm64/Kconfig | 1 +
drivers/acpi/Makefile | 1 +
drive
* Tony Lindgren [170929 15:35]:
> +static struct platform_driver sysc_driver = {
> + .probe = sysc_probe,
> + .driver = {
> + .name = "ti-sysc",
> + .of_match_table = sysc_match,
> + .pm = &sysc_pm_ops,
> + },
> +};
> +module_platf
On Fri, Oct 13, 2017 at 01:39:13PM -0400, Nicolas Pitre wrote:
> On Fri, 13 Oct 2017, Al Viro wrote:
>
> > On Thu, Oct 12, 2017 at 02:16:10AM -0400, Nicolas Pitre wrote:
> >
> > > static void cramfs_kill_sb(struct super_block *sb)
> > > {
> > > struct cramfs_sb_info *sbi = CRAMFS_SB(sb);
> >
On 10/13/2017 07:24 PM, Andy Lutomirski wrote:
On Fri, Oct 13, 2017 at 7:27 AM, Mathieu Desnoyers
wrote:
- On Oct 13, 2017, at 9:56 AM, Florian Weimer fwei...@redhat.com wrote:
On 10/13/2017 03:40 PM, Mathieu Desnoyers wrote:
The proposed ABI does not require to store any function pointe
On Fri, Oct 13, 2017 at 01:54:34PM +0200, Auger Eric wrote:
> Hi Christoffer,
> On 13/10/2017 13:44, Christoffer Dall wrote:
> > On Fri, Oct 06, 2017 at 05:29:02PM +0200, Auger Eric wrote:
> >> Hi,
> >>
> >> On 06/10/2017 16:37, Andre Przywara wrote:
> >>> Hi,
> >>>
> >>> On 27/09/17 14:28, Eric Au
> -Original Message-
> From: linus...@gmail.com [mailto:linus...@gmail.com] On Behalf Of Linus
> Torvalds
> Sent: Tuesday, October 10, 2017 4:17 PM
> To: Tobin C. Harding
> Cc: kernel-harden...@lists.openwall.com; KVM list ;
> Linux Kernel Mailing List ; Kees Cook
> ; Paolo Bonzini ; Tyc
On Fri, Oct 13, 2017 at 04:22:25PM +0200, Auger Eric wrote:
> Hi,
>
> On 13/10/2017 15:16, Christoffer Dall wrote:
> > On Wed, Sep 27, 2017 at 03:28:33PM +0200, Eric Auger wrote:
> >> At the moment the device table save() returns -EINVAL if
> >> vgic_its_check_id() fails to return the gpa of the e
In older versions of the kernel, event filtering by
pid does not use the set_event_pid file. Instead,
ftrace uses a common filter (created in make_pid_filter)
to filter events based on PID.
The syntax of the filter generated by this function is
overly permissive. When filtering by pid, || is used
Tony Lindgren wrote on Fri [2017-Oct-13 09:56:54 -0700]:
> * Benoit Parrot [171012 12:28]:
> > This patch adds the required hwmod nodes to support the Camera
> > Adaptation Layer (CAL) for the DRA72 family of devices.
> ...
>
> > +static struct omap_hwmod_class_sysconfig dra7xx_cal_sysc = {
> >
* Rafael J. Wysocki [171013 06:32]:
> [+cc Tony]
>
> On Friday, October 13, 2017 5:04:41 AM CEST Bjorn Helgaas wrote:
> > [+cc Rafael, linux-pm]
> > On Mon, Sep 11, 2017 at 11:10:27PM +0800, Jeffy Chen wrote:
> > > Add support for PCIE_WAKE pin in rockchip pcie driver.
...
> > > @@ -995,6 +996,15
Hi Vivien,
> >> > +REG_WRITE(REG_GLOBAL, GLOBAL_MAC_01, (addr[0] << 9) |
> >> addr[1]);
> >>
> >> Is that supposed to be 9 ?
> >
> > Looks like it.
> > Check
> http://www.marvell.com/switching/assets/marvell_linkstreet_88E6060_data
> sheet.pdf
>
> Hum, David is correct, there is a bug in
On Fri, Oct 13, 2017 at 05:34:44PM +0200, Auger Eric wrote:
> Hi Christoffer,
>
> On 13/10/2017 17:19, Christoffer Dall wrote:
> > On Wed, Sep 27, 2017 at 03:28:38PM +0200, Eric Auger wrote:
> >> When the GITS_BASER.Valid gets cleared, the data structures in
> >> guest RAM are not provisionned any
Tony Lindgren wrote on Fri [2017-Oct-13 10:01:13 -0700]:
> * Benoit Parrot [171012 12:29]:
> > HWSUP on this domain is only working when VIP1 probes.
> > If only VIP2 on DRA74x or CAL on DRA72x probes the domain does
> > not get enabled. This might indicates an issue in the HW Auto
> > state-mach
On Fri, Oct 13, 2017 at 05:41:10PM +0200, Auger Eric wrote:
> Hi Christoffer,
>
> On 13/10/2017 17:26, Christoffer Dall wrote:
> > Hi Eric,
> >
> > On Wed, Sep 27, 2017 at 03:28:39PM +0200, Eric Auger wrote:
> >> At the moment, the in-kernel emulated ITS is not properly reset.
> >> On guest resta
On Fri, Oct 13, 2017 at 10:43 AM, Dan Williams wrote:
> On Fri, Oct 13, 2017 at 10:01 AM, Al Viro wrote:
>> On Fri, Oct 13, 2017 at 08:56:10AM -0700, Dan Williams wrote:
>>> While implementing MAP_DIRECT, an mmap flag that arranges for an
>>> FL_LAYOUT lease to be established, Al noted:
>>>
>>>
Right now there is a way to add some CFLAGS that affect target builds,
but no way to add CFLAGS that affect host builds. Let's add a way.
We'll document two environment variables: CFLAGS_HOST and
CXXFLAGS_HOST.
We'll document that these variables get appended to by the kernel to
make the final CF
* Benoit Parrot [171013 11:01]:
> Tony Lindgren wrote on Fri [2017-Oct-13 10:01:13 -0700]:
> > * Benoit Parrot [171012 12:29]:
> > > HWSUP on this domain is only working when VIP1 probes.
> > > If only VIP2 on DRA74x or CAL on DRA72x probes the domain does
> > > not get enabled. This might indic
Tony Lindgren wrote on Fri [2017-Oct-13 10:05:13 -0700]:
> * Benoit Parrot [171012 12:28]:
> > +static struct omap_hwmod_class_sysconfig dra7xx_vpe_sysc = {
> > + .sysc_offs = 0x0010,
> > + .sysc_flags = (SYSC_HAS_MIDLEMODE | SYSC_HAS_SIDLEMODE),
> > + .idlemodes = (SIDLE_FORC
When hw queue is busy, we shouldn't take requests from
scheduler queue any more, otherwise it is difficult to do
IO merge.
This patch fixes the awful IO performance on some
SCSI devices(lpfc, qla2xxx, ...) when mq-deadline/kyber
is used by not taking requests if hw queue is busy.
Reviewed-by: Oma
Hi Jens,
In Red Hat internal storage test wrt. blk-mq scheduler, we found that I/O
performance is much bad with mq-deadline, especially about sequential I/O
on some multi-queue SCSI devcies(lpfc, qla2xxx, SRP...)
Turns out one big issue causes the performance regression: requests are
still dequeu
So that it becomes easy to support to dispatch from sw queue in the
following patch.
No functional change.
Reviewed-by: Bart Van Assche
Reviewed-by: Omar Sandoval
Suggested-by: Christoph Hellwig # for simplifying dispatch logic
Signed-off-by: Ming Lei
---
block/blk-mq-sched.c | 43 ++
We need to iterate ctx starting from any ctx in round robin
way, so introduce this helper.
Reviewed-by: Omar Sandoval
Cc: Omar Sandoval
Signed-off-by: Ming Lei
---
include/linux/sbitmap.h | 64 -
1 file changed, 47 insertions(+), 17 deletions(-)
We need to tell blk-mq for reserving resource before queuing
one request, so implement these two callbacks. Then blk-mq
can avoid to dequeue request earlier, and IO merge can
be improved a lot.
Signed-off-by: Ming Lei
---
drivers/scsi/scsi_lib.c | 75 ++---
For SCSI devices, there is often per-request-queue depth, which need
to be respected before queuing one request.
The current blk-mq always dequeues request first, then calls .queue_rq()
to dispatch the request to lld. One obvious issue of this way is that I/O
merge may not be good, because when th
SCSI devices use host-wide tagset, and the shared driver tag space is
often quite big. Meantime there is also queue depth for each lun(
.cmd_per_lun), which is often small, for example, on both lpfc and
qla2xxx, .cmd_per_lun is just 3.
So lots of requests may stay in sw queue, and we always flush
In the following patch, we will implement scsi_get_budget()
which need to call scsi_prep_state_check() when rq isn't
dequeued yet.
Signed-off-by: Ming Lei
---
drivers/scsi/scsi_lib.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/scsi/scsi_lib.c b/drivers/scsi/sc
Julia,
On 10/13/2017 08:55 AM, Julia Lawall wrote:
It seems that the then and else branches of the conditions on lines 920
and 932 are the same.
I think line 923 should be using RTL_RC_VHT_RATE_2SS_MCS8 rather than
RTL_RC_VHT_RATE_2SS_MCS9, but I have sent an inquiry to my contact at Realtek
Hi heiko,
On 10/13/2017 09:25 PM, Heiko Stuebner wrote:
does this actually work with mainline kernel sources?
Sean Paul did look at making the edp work on Chromebooks recently,
but it seemed there were still parts missing to make it actually display
something.
yes, it works, but only for boot
On 10/12/2017 03:59 PM, Mark Salyzyn wrote:
Move compiler-specific code to a local compiler.h file. CONFIG_AEABI
dependency check. System call fallback functions standardized into
a DEFINE_FALLBACK macro. Accept that __arch_counter_get_cntvct()
is the API for aarch64. Deal with unresolved referen
On Fri, Oct 13, 2017 at 10:53 AM, Florian Weimer wrote:
> On 10/13/2017 07:24 PM, Andy Lutomirski wrote:
>>
>> On Fri, Oct 13, 2017 at 7:27 AM, Mathieu Desnoyers
>> wrote:
>>>
>>> - On Oct 13, 2017, at 9:56 AM, Florian Weimer fwei...@redhat.com
>>> wrote:
>>>
On 10/13/2017 03:40 PM, Math
As for mv88e6xxx, setup the switch from within the mv88e6060 driver with
a random MAC address, and remove the .set_addr implementation.
Signed-off-by: Vivien Didelot
---
drivers/net/dsa/mv88e6060.c | 43 ++-
1 file changed, 26 insertions(+), 17 deletions(-
The .set_addr function does nothing, remove the dsa_loop implementation
before getting rid of it completely in DSA.
Signed-off-by: Vivien Didelot
---
drivers/net/dsa/dsa_loop.c | 8
1 file changed, 8 deletions(-)
diff --git a/drivers/net/dsa/dsa_loop.c b/drivers/net/dsa/dsa_loop.c
inde
Hi guys,
it looks like the suspend sequence depends on the dt node sequence, and
we are putting display-subsystem dt node above spi dt node, so it would
be earlier in the device list, then got suspended later than spi device.
the pwm backlight and cros_ec_spi pwm are very interesting, not onl
On Fri, 13 Oct 2017, Al Viro wrote:
> On Fri, Oct 13, 2017 at 01:39:13PM -0400, Nicolas Pitre wrote:
> > On Fri, 13 Oct 2017, Al Viro wrote:
> >
> > > On Thu, Oct 12, 2017 at 02:16:10AM -0400, Nicolas Pitre wrote:
> > >
> > > > static void cramfs_kill_sb(struct super_block *sb)
> > > > {
> > >
An Ethernet switch may support having a MAC address, which can be used
as the switch's source address in transmitted full-duplex Pause frames.
If a DSA switch supports the related .set_addr operation, the DSA core
sets the master's MAC address on the switch.
This won't make sense anymore in a mul
An Ethernet switch may support having a MAC address, which can be used
as the switch's source address in transmitted full-duplex Pause frames.
If a DSA switch supports the related .set_addr operation, the DSA core
sets the master's MAC address on the switch. This won't make sense
anymore in a mult
The 88E6060 Ethernet switch always transmits the multicast bit of the
switch MAC address as a zero. It re-uses the corresponding bit 8 of the
register "Switch MAC Address Register Bytes 0 & 1" for "DiffAddr".
If the "DiffAddr" bit is 0, then all ports transmit the same source
address. If it is set
Now that there is no user for the .set_addr function, remove it from
DSA. If a switch supports this feature (like mv88e6xxx), the
implementation can be done in the driver setup.
Signed-off-by: Vivien Didelot
---
include/net/dsa.h | 1 -
net/dsa/dsa2.c| 6 --
net/dsa/legacy.c | 6 --
Pavel Tatashin wrote: [Fri Oct 13 2017, 01:32:03PM EDT]
> Changelog:
> v12 - v11
> - Improved comments for mm: zero reserved and unavailable struct pages
> - Added back patch: mm: deferred_init_memmap improvements
> - Added patch from Will Deacon: arm64: kasan: Avoid using
> vmemmap_populate to
On Fri, 13 Oct 2017 13:57:12 -0400
Will Hawkins wrote:
> In older versions of the kernel, event filtering by
> pid does not use the set_event_pid file. Instead,
> ftrace uses a common filter (created in make_pid_filter)
> to filter events based on PID.
>
> The syntax of the filter generated by t
On 10/14/2017 02:19 AM, jeffy wrote:
it looks like the suspend sequence depends on the dt node sequence, and
we are putting display-subsystem dt node above spi dt node, so it would
be earlier in the device list, then got suspended later than spi device.
the pwm backlight and cros_ec_spi pwm ar
On 10/13/2017 03:50 AM, rui_f...@realsil.com.cn wrote:
From: rui_feng
Add support for new chip rts5260.
In order to support rts5260，the definitions of some internal
registers and workflow have to be modified and are different from its
predecessors and OCP function is added for RTS5260.
So we ne
On Fri, Oct 13, 2017 at 2:35 AM, Ben Maurer wrote:
>
> I'm really excited to hear that you're open to this patch set and totally
> understand the desire for some more numbers.
So the patch-set actually looks very reasonable today. I looked
through it (ok, I wasn't cc'd on the ppc-only patches so
This is a follow-up to commit 5c4994102fb5 ("posix-timers:
Use get_timespec64() and put_timespec64()"), which left two
system call using copy_from_user()/copy_to_user(). We can
change them as well for consistency.
Signed-off-by: Arnd Bergmann
---
kernel/time/posix-stubs.c | 20 --
On Sat, Oct 14, 2017 at 02:19:28AM +0800, jeffy wrote:
> Hi guys,
>
> it looks like the suspend sequence depends on the dt node sequence, and we
> are putting display-subsystem dt node above spi dt node, so it would be
> earlier in the device list, then got suspended later than spi device.
Would
On Fri, 2017-10-13 at 08:56 -0700, Dan Williams wrote:
> While implementing MAP_DIRECT, an mmap flag that arranges for an
> FL_LAYOUT lease to be established, Al noted:
>
> You are not even guaranteed that descriptor will remain be still
> open by the time you pass it down to your helper,
On Sat, Oct 14, 2017 at 02:25:48AM +0800, jeffy wrote:
> On 10/14/2017 02:19 AM, jeffy wrote:
> >
> >
> > it looks like the suspend sequence depends on the dt node sequence, and
> > we are putting display-subsystem dt node above spi dt node, so it would
> > be earlier in the device list, then got
On Fri, Oct 13, 2017 at 2:24 PM, Steven Rostedt wrote:
>
> On Fri, 13 Oct 2017 13:57:12 -0400
> Will Hawkins wrote:
>
> > In older versions of the kernel, event filtering by
> > pid does not use the set_event_pid file. Instead,
> > ftrace uses a common filter (created in make_pid_filter)
> > to f
Hi Rafael,
On 10/13/2017 09:21 PM, Rafael J. Wysocki wrote:
I'm a little skeptical about dev_pm_set_dedicated_wake_irq(), not
because I know anything at all about it, but because there are only
five callers in the whole tree, three of which are in UART code, and
none in anything resembling PCI
From 5bb71b55a21adae6858bc008834b8806abbb4405 Mon Sep 17 00:00:00 2001
From: Eric Sesterhenn
Date: Fri, 13 Oct 2017 20:31:07 +0200
Subject: [PATCH] Prevent out of bound reads in asn1_decoder
In some cases the asn1_decoder supplies the callback
functions with invalid parameters, which causes them
do_settimeofday is a wrapper around do_settimeofday64, so
we can simply call that function directly, and kill off the
wrapper once the last user is one.
Signed-off-by: Arnd Bergmann
---
kernel/time/time.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/kernel/tim
A surprise link down may retrain very quickly causing the same slot
generate a link up event before handling the link down event completes.
Since the link is active, the power off work queued from the first link
down will cause a second down event when power is disabled. However, the
link up event
One can ask more buses to be reserved for hotplug bridges by passing
pci=hpbussize=N in the kernel command line. However, if the parent bus
does not have enough bus space available we still create child bus with
the requested number of subordinate buses.
In the example below hpbussize is set to on
During surprise hot-unplug the device is not there anymore. When that
happens we read 0x from the registers and pciehp_unconfigure_device()
inadvertently thinks the device is a display device because bridge
control register returns 0xff refusing to remove it:
pciehp :00:1c.0:pcie004:
It is possible that the hotplug event has already happened before the
driver is attached to a PCIe hotplug downstream port. If we just clear
the status we never get the hotplug interrupt and thus the event will be
missed.
To make sure that does not happen, we leave Presence Detect Changed bit
unto
The current scanning code is really hard to understand because it calls
the same function in a loop where pass value is changed without any
comments explaining it:
for (pass = 0; pass < 2; pass++)
for_each_pci_bridge(dev, bus)
max = pci_scan_bridge(bus, dev, max, pass);
The same problem that we have with bus space, applies to other resources
as well. Linux only allocates the minimal amount of resources so that
the devices currently present barely fit there. This prevents extending
the chain later on because the resource windows allocated for hotplug
downstream por
System BIOS sometimes allocates extra bus space for hotplug capable PCIe
root/downstream ports. This space is needed if the device plugged to the
port will have more hotplug capable downstream ports. A good example of
this is Thunderbolt. Each Thunderbolt device contains a PCIe switch and
one or mo
There is not much point of having a file with a single function in it.
Instead we can just move pci_hp_add_bridge() to drivers/pci/probe.c and
make it available always when PCI core is enabled.
Signed-off-by: Mika Westerberg
---
drivers/pci/Makefile | 3 ---
drivers/pci/hotplug-pci.c | 29
Currently when plugging PCIe device using native PCIe hotplug Linux PCI
core tries to allocate bus space and resources so that the newly enumerated
topology barely fits there. Now, if the PCIe topology that was just plugged
in has more PCIe hotplug ports we will run out of bus space and resources
p
On Fri, Oct 13, 2017 at 11:30:06AM -0700, Dmitry Torokhov wrote:
> On Sat, Oct 14, 2017 at 02:19:28AM +0800, jeffy wrote:
> > > Yeah, it's the same stuff as we get with initcall ordering. This sort
> > > of thing does happen with things like PMICs which tend to have hardware
> > > that the system
The hypercall was added using a struct timespec based implementation,
but we should not use timespec in new code.
This changes it to timespec64. There is no functional change
here since the implementation is only used in 64-bit kernels
that use the same definition for timespec and timespec64.
Fix
On Mon, Oct 09, 2017 at 09:26:14PM +0200, Clemens Gruber wrote:
> The arguments for SDA and SCL were swapped. Fix it.
>
> Signed-off-by: Clemens Gruber
Applied to for-current, thanks!
signature.asc
Description: PGP signature
In older versions of the kernel, event filtering by
pid does not use the set_event_pid file. Instead,
ftrace uses a common filter (created in make_pid_filter)
to filter events based on PID.
The syntax of the filter generated by this function is
overly permissive. When filtering by pid, || is used
The x86 platform operations are fairly isolated, so we can
change them from using timespec to timespec64. I checked that
All the users and callers are safe, and there is only one
critical function that is broken beyond 2106:
pvclock_read_wallclock() uses a 32-bit number of seconds since
the epoch
On Fri, Oct 13, 2017 at 11:04 AM, Masahiro Yamada
wrote:
> Hi Rob,
>
>
> 2017-10-13 22:49 GMT+09:00 Rob Herring :
>> On Fri, Oct 06, 2017 at 02:02:58PM +0900, Keiji Hayashibara wrote:
>>> Add uniphier-efuse dt-bindings documentation.
>>>
>>> Signed-off-by: Keiji Hayashibara
>>> ---
>>> .../devic
> #include
> #include
> #include
> +#include
> +#include
Please keep the sorting. Rest looks good.
signature.asc
Description: PGP signature
On Fri, 2017-10-13 at 13:37 +0200, Borislav Petkov wrote:
> On Thu, Oct 12, 2017 at 06:08:17PM -0700, Ricardo Neri wrote:
> >
> > In my opinion it would be better to have all the checks in a single place.
> > This
> > makes the code easier to read that having this special case directly
> > in reso
Hi Dmitry,
On 10/14/2017 02:30 AM, Dmitry Torokhov wrote:
On Sat, Oct 14, 2017 at 02:19:28AM +0800, jeffy wrote:
Hi guys,
it looks like the suspend sequence depends on the dt node sequence, and we
are putting display-subsystem dt node above spi dt node, so it would be
earlier in the device lis
The ep_poll_safewake() function is used to wakeup potentially nested epoll
file descriptors. The function uses ep_call_nested() to prevent entering
the same wake up queue more than once, and to prevent excessively deep
wakeup paths (deeper than EP_MAX_NESTS). However, this is not necessary
since we
On Tue, Oct 10, 2017 at 06:11:15PM +0200, Ricardo Ribalda Delgado wrote:
> SMBUS_BLOCK_DATA transactions might fail due to a race condition with
> the IMC (Integrated Micro Controller), even when the IMC semaphore
> is used.
>
> This bug has been reported and confirmed by AMD, who suggested as a
>
On Wed, Oct 04, 2017 at 08:13:57AM -0500, Brijesh Singh wrote:
> Define Secure Encrypted Virtualization (SEV) key management command id
> and structure. The command definition is available in SEV KM [1] spec
> 0.14 and Documentation/virtual/kvm/amd-memory-encryption.txt
>
> [1] http://support.amd.
On Thu, 2017-10-12 at 13:16 +1100, Tobin C. Harding wrote:
> On Wed, Oct 11, 2017 at 06:02:47PM +0530, Shreeya Patel wrote:
> >
> > On Tue, 2017-10-10 at 11:06 +1100, Tobin C. Harding wrote:
> > >
> > > On Tue, Oct 10, 2017 at 02:48:58AM +0530, Shreeya Patel wrote:
> > > >
> > > >
> > > > Remov
On Sat, Jul 15, 2017 at 04:51:26PM -0700, Guenter Roeck wrote:
> AMD Family 17h uses the KERNCZ SMBus controller. While its documentation
> is not publicly available, it is documented in the BIOS and Kernel
> Developer’s Guide for AMD Family 15h Models 60h-6Fh Processors.
>
> On this SMBus control
* Benoit Parrot [171013 11:06]:
> Tony Lindgren wrote on Fri [2017-Oct-13 10:05:13 -0700]:
> > * Benoit Parrot [171012 12:28]:
> > > +static struct omap_hwmod_class_sysconfig dra7xx_vpe_sysc = {
> > > + .sysc_offs = 0x0010,
> > > + .sysc_flags = (SYSC_HAS_MIDLEMODE | SYSC_HAS_SIDLEMODE)
Hi guys,
so what happens here is:
1/ we put display-subsystem dt node before spi node, which cause
rockchip drm driver probed before spi(also before edp driver/vop driver...)
2/ rockchip drm driver bound after spi/edp/vop... drivers probed
3/ in rockchip drm driver's resume callback, it would
On Tue, Oct 10, 2017 at 06:11:15PM +0200, Ricardo Ribalda Delgado wrote:
> SMBUS_BLOCK_DATA transactions might fail due to a race condition with
> the IMC (Integrated Micro Controller), even when the IMC semaphore
> is used.
>
> This bug has been reported and confirmed by AMD, who suggested as a
>
On Fri, Oct 13, 2017 at 09:03:26PM +0200, Wolfram Sang wrote:
> On Tue, Oct 10, 2017 at 06:11:15PM +0200, Ricardo Ribalda Delgado wrote:
> > SMBUS_BLOCK_DATA transactions might fail due to a race condition with
> > the IMC (Integrated Micro Controller), even when the IMC semaphore
> > is used.
> >
On Fri, Oct 06, 2017 at 01:51:32PM +0200, Geert Uytterhoeven wrote:
> Document support for the Interrupt Controller for Externel Devices
> (INTC-EX) in the Renesas M3-W (r8a7796), V3M (r8a77970), and D3
> (r8a77995) SoCs.
>
> No driver update is needed.
>
> Signed-off-by: Geert Uytterhoeven
> --
Hi,
I had found an issue during assigning mpt3sas controllers as DDA on
fedora-25 VM with kernel(4.11.x/4.14.0-rc4+) on microsoft Hyperv 2016.
Below is the logs after insmod of mpt3sas and pci-hyperv on
upstream(4.14.0-rc4+) kernel,
# dmesg
[ 37.442924] hv_vmbus: registering driver hv_pci
[ 3
> -Original Message-
> From: netdev-ow...@vger.kernel.org [mailto:netdev-
> ow...@vger.kernel.org] On Behalf Of Vivien Didelot
> Sent: Friday, October 13, 2017 1:39 PM
> To: net...@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org; ker...@savoirfairelinux.com; David S.
> Miller; Florian Fa
klp_complete_transition() performs a bit of housework before a
transition to KLP_PATCHED or KLP_UNPATCHED is actually completed
(including post-(un)patch callbacks). To be consistent, move the
transition "complete" kernel log notice out of
klp_try_complete_transition() and into klp_complete_transi
701 - 800 of 1004 matches
Mail list logo
