Hi All,
Shared virtual memory (SVM) space between devices and applications can
reduce programming complexity and enhance security. To enable SVM in
the guest, i.e. shared guest application address space and physical
device DMA address, IOMMU driver must provide some new functionalities.
This patc
Device faults detected by IOMMU can be reported outside IOMMU
subsystem. This patch intends to provide a generic device
fault data such that device drivers can communicate IOMMU faults
without model specific knowledge.
The assumption is that model specific IOMMU driver can filter and
handle most o
DMA faults can be detected by IOMMU at device level. Adding a pointer
to struct device allows IOMMU subsystem to report relevant faults
back to the device driver for further handling.
For direct assigned device (or user space drivers), guest OS holds
responsibility to handle and respond per device
Signed-off-by: Jacob Pan
---
drivers/iommu/dmar.c| 53 ++---
drivers/iommu/intel-iommu.c | 3 ++-
include/linux/intel-iommu.h | 10 +++--
3 files changed, 60 insertions(+), 6 deletions(-)
diff --git a/drivers/iommu/dmar.c b/drivers/iommu/dmar.
Virtual IOMMU was proposed to support Shared Virtual Memory (SVM)
use in the guest:
https://lists.gnu.org/archive/html/qemu-devel/2016-11/msg05311.html
As part of the proposed architecture, when an SVM capable PCI
device is assigned to a guest, nested mode is turned on. Guest owns the
first level
Add Intel VT-d ops to the generic iommu_bind_pasid_table API
functions.
The primary use case is for direct assignment of SVM capable
device. Originated from emulated IOMMU in the guest, the request goes
through many layers (e.g. VFIO). Upon calling host IOMMU driver, caller
passes guest PASID tabl
On Thu, Oct 05, 2017 at 03:31:05PM -0700, Linus Torvalds wrote:
> On Thu, Oct 5, 2017 at 1:57 PM, Al Viro wrote:
> >
> > AFAICS, the real bug here is in hugetlbfs; that's where obscene values in
> > ->f_bsize come from. IMO all that code in put_compat_statfs64() should be
> > replaced with
> >
On Fri, Oct 06, 2017 at 12:41:56AM +0200, Thomas Gleixner wrote:
> On Thu, 5 Oct 2017, Andi Kleen wrote:
> > +/*
> > + * Table of CPUID features that depend on others.
> > + *
> > + * This only includes dependencies that can be usefully disabled, not
> > + * features part of the base set (like FPU)
On Thu, Sep 28, 2017 at 03:07:27PM +0200, Andrzej Hajda wrote:
> These bindings allows to describe most known standard USB connectors
> and it should be possible to extend it if necessary.
> USB connectors, beside USB can be used to route other protocols,
> for example UART, Audio, MHL. In such cas
In preparation for unconditionally passing the struct timer_list pointer to
all timer callbacks, switch to using the new timer_setup() and from_timer()
to pass the timer pointer explicitly.
Cc: Jens Axboe
Cc: "Ed L. Cashin"
Cc: linux-bl...@vger.kernel.org
Cc: Thomas Gleixner
Signed-off-by: Kees
2017-10-06 2:14 GMT+08:00 Radim Krčmář :
> 2017-10-05 07:35-0700, Wanpeng Li:
>> From: Wanpeng Li
>>
>> The description in the Intel SDM of how the divide configuration
>> register is used: "The APIC timer frequency will be the processor's bus
>> clock or core crystal clock frequency divided by th
Hi,
This series abolishes jprobe APIs and remove or disable related
code. This is a preparation of removing all jprobe code (including
kprobe's break_handler.)
I'm not so sure how many jprobe users still exists, but
please migrate your tool to trace-event or perf-probe.
As we discussed this threa
Use ENOTSUPP instead of ENOSYS because ENOSYS is reserved
only for invalid syscall number.
Signed-off-by: Masami Hiramatsu
---
include/linux/kprobes.h | 16
kernel/kprobes.c|4 ++--
2 files changed, 10 insertions(+), 10 deletions(-)
diff --git a/include/linux/kpro
Abolish jprobe APIs and comment out the jprobe API function
code. This is a preparation of removing all jprobe related
code (including kprobe's break_handler)
Nowadays ftrace and other tracing features are enough matured
to replace jprobe use-cases. Users can safely use ftrace and
perf probe etc.
Disable jprobe test code because jprobe is deprecated.
This code will be completely removed when jprobe code
is removed.
Signed-off-by: Masami Hiramatsu
---
kernel/test_kprobes.c |9 -
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/kernel/test_kprobes.c b/kernel/test_kp
Remove jprobe sample module because jprobe is deprecated.
Signed-off-by: Masami Hiramatsu
---
samples/kprobes/Makefile |2 +
samples/kprobes/jprobe_example.c | 67 --
2 files changed, 1 insertion(+), 68 deletions(-)
delete mode 100644 samples/kp
In preparation for unconditionally passing the struct timer_list pointer to
all timer callbacks, switch to using the new timer_setup() and from_timer()
to pass the timer pointer explicitly.
Cc: Jens Axboe
Cc: Michal Hocko
Cc: Andrew Morton
Cc: Jan Kara
Cc: Johannes Weiner
Cc: Nicholas Piggin
Remove jprobe related documentations from kprobes.txt.
It also add some migration advice for the people who still
using jprobe.
Signed-off-by: Masami Hiramatsu
---
Documentation/kprobes.txt | 153 +++--
1 file changed, 51 insertions(+), 102 deletions(-)
On Thu, 2017-10-05 at 08:50 -0400, Steven Rostedt wrote:
> On Wed, 04 Oct 2017 15:24:23 -0500
> Scott Wood wrote:
>
> > It should also be noted that ktest.pl only depends on config-
> > bisect.pl
> > if a config bisect is being performed, so other ktest.pl functions
> > still
> > work standalone.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git
dev.2017.10.05a
head: 39ae2675aa536e6ef9d334fe9097d1e2c6b25fbc
commit: 7e3675cc18bbf4d84f60bfc02ff563ae3764ad35 [32/34] locking/barriers: Kill
lockless_dereference
config: h8300-h8300h-sim_defconfig (attached as .conf
On Thu, Sep 28, 2017 at 02:11:27PM +0100, Sudeep Holla wrote:
> This patch adds ARM MHU specific mailbox client bindings to support
> SCMI. Since SCMI specification just requires doorbell mechanism from
> mailbox controllers, we add mailbox data to specify the doorbell bit(s).
>
> Cc: Rob Herring
Added functionality to read LPIT table, which provides:
- Sysfs interface to read residency counters via
/sys/devices/system/cpu/cpuidle/low_power_idle_cpu_residency_us
/sys/devices/system/cpu/cpuidle/low_power_idle_system_residency_us
Here the count "low_power_idle_cpu_residency_us" shows the ti
Hi Peter,
On Wed, Oct 4, 2017 at 9:01 AM, Peter Zijlstra wrote:
> On Fri, Sep 29, 2017 at 02:22:45PM -0700, Joel Fernandes wrote:
[...]
>> + */
>> +static DEFINE_PER_CPU(int, tracing_irq_cpu);
>> +
>> #if defined(CONFIG_TRACE_IRQFLAGS) && !defined(CONFIG_PROVE_LOCKING)
>> void trace_hardirqs_on
On Thu, Oct 5, 2017 at 4:28 PM, Joel Fernandes wrote:
> Hi Peter,
>
> On Wed, Oct 4, 2017 at 9:01 AM, Peter Zijlstra wrote:
>> On Fri, Sep 29, 2017 at 02:22:45PM -0700, Joel Fernandes wrote:
[...]
>>> EXPORT_SYMBOL(trace_hardirqs_off);
>>>
>>> __visible void trace_hardirqs_on_caller(unsigned lo
On Thu, Oct 05, 2017 at 01:08:20PM +0200, Wolfram Sang wrote:
> On Mon, Oct 02, 2017 at 04:23:43PM +0200, Gregory CLEMENT wrote:
> > Hi Wolfram,
> >
> > On ven., sept. 29 2017, Kalyan Kinthada
> > wrote:
> >
> > > This commit modifies the documentation for
> > > "marvell,mv78230-a0-i2c" compa
Only try to clean up the svm page request irq if one has
been assigned. Also clear pr_irq in the error path if irq request
fails.
Signed-off-by: Jerry Snitselaar
---
drivers/iommu/intel-svm.c | 9 ++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/drivers/iommu/intel-svm.c b
On Wed, Oct 04, 2017 at 08:50:49AM +0200, Laurent Dufour wrote:
> On 25/09/2017 18:27, Alexei Starovoitov wrote:
> > On Mon, Sep 18, 2017 at 12:15 AM, Laurent Dufour
> > wrote:
> >> Despite the unprovable lockdep warning raised by Sergey, I didn't get any
> >> feedback on this series.
> >>
> >> Is
On Thu, Sep 28, 2017 at 03:51:24PM -0700, Vikas Manocha wrote:
> This patch removes the extra compatibility string "st,stm32-usart" to
> avoid confusion, save some time & space.
I'm confused why you don't need it anymore. I thought the h/w blocks
were configured differently.
>
> Signed-off-by:
On Thu, Oct 5, 2017 at 4:13 PM, Masami Hiramatsu wrote:
> Hi,
>
> This series abolishes jprobe APIs and remove or disable related
> code. This is a preparation of removing all jprobe code (including
> kprobe's break_handler.)
> I'm not so sure how many jprobe users still exists, but
> please migra
Some CPUID features depend on other features. Currently it's
possible to to clear dependent features, but not clear the base features,
which can cause various interesting problems.
This patch implements a generic table to describe dependencies
between CPUID features, to be used by all code that cl
On Thu, Oct 5, 2017 at 7:21 AM, Tejun Heo wrote:
> On Wed, Oct 04, 2017 at 05:54:17PM -0700, Kees Cook wrote:
>> In preparation for unconditionally passing the struct timer_list pointer to
>> all timer callbacks, switch to using the new timer_setup() and from_timer()
>> to pass the timer pointer e
Explicitly casting pci_power_t types to resolve sparse warnings (shown
below).
Also fixing a related logging bug where pci_power_t is cast to unsigned
(can be negative, i.e. PCI_POWER_ERROR).
Original sparse report:
drivers/staging/irda/drivers//vlsi_ir.c:170:51: warning: cast from
restricted pc
On Thu, 05 Oct 2017 18:18:54 -0500
Scott Wood wrote:
> On Thu, 2017-10-05 at 08:50 -0400, Steven Rostedt wrote:
> > On Wed, 04 Oct 2017 15:24:23 -0500
> > Scott Wood wrote:
> >
> > > It should also be noted that ktest.pl only depends on config-
> > > bisect.pl
> > > if a config bisect is bein
Removing a comment that duplicates definitions for pci_power_t
enumeration, and pointing to the relevant header file (current comment
is also missing PCI_POWER_ERROR).
Signed-off-by: Matthew Giassa
---
drivers/staging/rtlwifi/pci.c | 7 +--
1 file changed, 1 insertion(+), 6 deletions(-)
dif
On Thursday, October 05, 2017, Nicolas Pitre wrote:
> Do you have the same amount of free memory once booted in both cases?
Yes, almost exactly the same, so obvious it must be working the same for
both cases. That's enough evidence for me.
Thanks.
Chris
On Thu, 5 Oct 2017 16:35:22 -0700
Kees Cook wrote:
> > As far as I can see, tcp probe, dccp probe, sctp probe and lkdtm
> > are using jprobe to probe function. Please consider to migrate.
>
> I'm happy to do so, but I'm quite unfamiliar with how to do this (I
> didn't write lkdtm's jprobe code
On Thu, Oct 05 2017, Matthias Kaehlcke wrote:
> The raid10 driver can't be built with clang since it uses a variable
> length array in a structure (VLAIS):
>
> drivers/md/raid10.c:4583:17: error: fields must have a constant size:
> 'variable length array in structure' extension will never be sup
A new feature Range Selector (RS) has been added to GIC specification
in order to support more than 16 CPUs at affinity level 0. New fields
are introduced in SGI system registers (ICC_SGI0R_EL1, ICC_SGI1R_EL1
and ICC_ASGI1R_EL1) to relax an artificial limit of 16 at level 0.
- A new RSS field in I
On Thu, Oct 5, 2017 at 4:58 PM, Steven Rostedt wrote:
> On Thu, 5 Oct 2017 16:35:22 -0700
> Kees Cook wrote:
>
>> > As far as I can see, tcp probe, dccp probe, sctp probe and lkdtm
>> > are using jprobe to probe function. Please consider to migrate.
>>
>> I'm happy to do so, but I'm quite unfamil
Hi Neil,
El Fri, Oct 06, 2017 at 10:58:59AM +1100 NeilBrown ha dit:
> On Thu, Oct 05 2017, Matthias Kaehlcke wrote:
>
> > The raid10 driver can't be built with clang since it uses a variable
> > length array in a structure (VLAIS):
> >
> > drivers/md/raid10.c:4583:17: error: fields must have a c
Daniel Drake :
[...]
> Also, is there a standard behaviour defined for ethernet drivers
> regarding wake-on-LAN? r8169 appears to enable wake-on-LAN by default
> if it believes the hardware is capable of it,
If so it isn't its designed behavior.
The r8169 driver does not enable specific WoL even
On Thu, 5 Oct 2017 16:35:22 -0700
Kees Cook wrote:
> On Thu, Oct 5, 2017 at 4:13 PM, Masami Hiramatsu wrote:
> > Hi,
> >
> > This series abolishes jprobe APIs and remove or disable related
> > code. This is a preparation of removing all jprobe code (including
> > kprobe's break_handler.)
> > I'm
Abdul Haleem writes:
> Hi,
>
> linux-next kernel panic while DLPAR CPU add/remove operation in a loop.
>
> Test: CPU hot-unplug
> Machine Type: Power8 PowerVM LPAR
> kernel: 4.14.0-rc2-next-20170928
> gcc : 5.2.1
>
> trace logs
> --
> cpu 10 (hwid 10) Ready to die...
> cpu 11 (hwid 11) Re
From: "K. Y. Srinivasan"
Miscellaneous enhancements and fixes.
K. Y. Srinivasan (1):
Drivers: hv: vmbus: Make pannic reporting to be more useful
Stephen Hemminger (2):
Drivers: hv: vmbus: Expose per-channel interrupts and events counters
vmbus: initialize reserved fields in messages
Doc
From: "K. Y. Srinivasan"
Hyper-V allows the guest to report panic and the guest can pass additional
information. All this is logged on the host. Currently Linux is passing back
information that is not particularly useful. Make the following changes:
1. Windows uses crash MSR P0 to report bugchec
From: Stephen Hemminger
When investigating performance, it is useful to be able to look at
the number of host and guest events per-channel. This is equivalent
to per-device interrupt statistics.
Signed-off-by: Stephen Hemminger
Signed-off-by: K. Y. Srinivasan
---
Documentation/ABI/stable/sysf
From: Stephen Hemminger
Make sure and initialize reserved fields in messages to host,
rather than passing stack junk.
Signed-off-by: Stephen Hemminger
Signed-off-by: K. Y. Srinivasan
---
drivers/hv/channel.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/hv/channel.c b/drivers/
These patches add trace events support for preempt and irq disable/enable
events.
Here's an example of how Android's systrace will be using it to show atomic
sections as a gantt chart: http://imgur.com/download/TZplEVp
Other advantages of this initial work could be rewriting of preemptirqs off
tra
Preempt and irq trace events can be used for tracing the start and
end of an atomic section which can be used by a trace viewer like
systrace to graphically view the start and end of an atomic section and
correlate them with latencies and scheduling issues.
This also serves as a prelude to using s
In preparation of adding irqsoff and preemptsoff enable and disable trace
events, move required functions and code to make it easier to add these events
in a later patch. This patch is just code movement and no functional change.
Cc: Steven Rostedt
Cc: Peter Zijlstra
Cc: kernel-t...@android.com
From: Bjorn Andersson
Date: Wed, 4 Oct 2017 20:51:05 -0700
> +/**
> + * struct qrtr_hdr_v2 - (I|R)PCrouter packet header later versions
> + * @version: protocol version
> + * @type: packet type; one of QRTR_TYPE_*
> + * @flags: bitmask of QRTR_FLAGS_*
> + * @optlen: length of optional header dat
The kvm slabs can consume a significant amount of system memory
and indeed in our production environment we have observed that
a lot of machines are spending significant amount of memory that
can not be left as system memory overhead. Also the allocations
from these slabs can be triggered directly
On Mon, Oct 2, 2017 at 10:32 PM, Hannes Reinecke wrote:
> On 09/27/2017 09:33 AM, Gavin Guo wrote:
>> There is a problem in the latest upstream kernel with the device:
>>
>> $ grep -i lsi lspci
>> 03:00.0 Serial Attached SCSI controller [0107]: LSI Logic / Symbios
>> Logic SAS1068 PCI-X Fusion-MPT
This patch series fixes some logging bugs and adds some missing message
severity levels.
There are also cleanup patches for dead code and some Kconfig cruft.
Custom debug message logging is converted to netif_* calls to reduce
code duplication.
All up, about 150 lines of code are eliminated.
Th
Signed-off-by: Finn Thain
---
drivers/net/ethernet/cirrus/mac89x0.c | 31 ---
1 file changed, 31 deletions(-)
diff --git a/drivers/net/ethernet/cirrus/mac89x0.c
b/drivers/net/ethernet/cirrus/mac89x0.c
index f910f0f386d6..4fd72c1a69f5 100644
--- a/drivers/net/ethernet
On Thu, Oct 05, 2017 at 01:42:09PM -0500, Bjorn Helgaas wrote:
>On Thu, Oct 05, 2017 at 11:05:12PM +0800, Wei Yang wrote:
>> On Wed, Oct 4, 2017 at 5:15 AM, Bjorn Helgaas wrote:
>> > [+cc Alex, Gavin, Wei]
>> >
>> > On Fri, Sep 29, 2017 at 10:49:38PM -0700, Govindarajulu Varadarajan wrote:
>> >> C
On Fri, 6 Oct 2017 09:32:52 +0900
Masami Hiramatsu wrote:
> I think using ftrace gives you lower latency, but you need to depend on
> CONFIG_FUNCTION_TRACER instead of CONFIG_KPROBES.
Which shouldn't be an issue, since all distros now have that enabled.
-- Steve
Also eliminate duplicated debug code by moving it into the core driver.
Cc: Thomas Bogendoerfer
Cc: Chris Zankel
Signed-off-by: Finn Thain
---
Only the sonic.[ch] and macsonic.c changes have been tested. The other
changes are similar but untested.
---
drivers/net/ethernet/natsemi/jazzsonic.c |
Before expansion, dev->name is "eth%d", so log the slot number instead.
Log the MAC address after the interface gets a meaningful name.
Disambiguate the two identical "Card type %s is unsupported" messages.
Fix the duplicated driver name in the pr_warn() message.
Fixes: 3a3a7f3b7fbd ("net: mac8390
The patch which introduced the 8390 core module parameter 'msg_enable'
failed to do anything useful with it: it merely causes an ancient
version string to be logged.
Remove the other code that logs the same string. Use the msg_enable
module parameter as the default value for ei_local->msg_enable.
Log the MAC address after the interface gets a meaningful name
and in doing so, make the registration error path more idiomatic.
Drop redundant debug messages for FIFO events recorded in the
interface statistics (consistent with mace.c).
Signed-off-by: Finn Thain
Tested-by: Stan Johnson
---
dri
Add missing printk severity levels.
Don't print the valid silicon revision number (it's in the source).
Avoid KERN_CONT usage as per advice from checkpatch.
Avoid ifdef around printk calls.
Cc: Thomas Bogendoerfer
Cc: Chris Zankel
Signed-off-by: Finn Thain
---
Only the macsonic.c changes have b
Signed-off-by: Finn Thain
---
drivers/net/ethernet/cirrus/mac89x0.c | 47 ---
1 file changed, 16 insertions(+), 31 deletions(-)
diff --git a/drivers/net/ethernet/cirrus/mac89x0.c
b/drivers/net/ethernet/cirrus/mac89x0.c
index fa4b6968afd5..d331c8344b96 100644
---
The only version of smc9194.c with Mac support is the one in the
linux-mac68k CVS repo. AFAIK that driver never made it to the mainline.
Despite that, as of v2.3.45, arch/m68k/config.in listed CONFIG_SMC9194
under CONFIG_MAC. This mistake got carried over into Kconfig in v2.5.55.
(See pre-git era
Fix misplaced newlines in conditional log messages.
Add missing printk severity levels.
Log the MAC address after the interface gets a meaningful name.
Drop deprecated "out of memory" message as per checkpatch advice.
Signed-off-by: Finn Thain
---
drivers/net/ethernet/cirrus/mac89x0.c | 26 +
From: Masaki Ota
-Define T4 device specification value for support T4 device.
-Create "t4_contact_data" and "t4_input_report" structure for decode T4 data
and store it.
-Create "t4_calc_check_sum()" function for calculate checksum value to send the
device. T4 needs to send this value when read/w
From: Masaki Ota
-Add T4 USB device Product ID. (0x1216)
-Separate T4 USB device initialization code from T4 Standard device code.
-T4 USB device is used on HP Elite x2 series
Signed-off-by: Masaki Ota
---
drivers/hid/hid-alps.c | 35 +--
drivers/hid/hid-core.c
From: Masaki Ota
-Create x_min, y_min and max_fingers variables for set correct XY minimum value
and the number of max finger on each devices.
-Move the Button pad checking code to U1 init function, because this checking
code is for U1 device.
Signed-off-by: Masaki Ota
---
drivers/hid/hid-alp
I have modified the Patch.
About __maybe_unused annotation, it was specified by Benjamin in previous
review.
So I added this annotation.
Best Regards,
Masaki OTa
From: Masaki Ota
-Move some variables(dev_ctrl, dev_type, sen_line_num_x, sen_line_num_y,
pitch_x, pitch_y, resolution, btn_info) from u1_dev structure to "u1_init()",
because these variables are only used in "u1_init()" function.
Signed-off-by: Masaki Ota
---
drivers/hid/hid-alps.c | 67
From: Masaki Ota
-Create "static int u1_init()" function for separate U1 device initialization
code from Main initialization.
-Create "has_sp" variable for checking whether it has SP device or not.
Signed-off-by: Masaki Ota
---
drivers/hid/hid-alps.c | 120 +++--
From: Masaki Ota
-Add new U1 device Product ID
-This device is used on HP Elite book x360 series
Signed-off-by: Masaki Ota
---
drivers/hid/hid-alps.c | 3 +++
drivers/hid/hid-core.c | 1 +
drivers/hid/hid-ids.h | 1 +
3 files changed, 5 insertions(+)
diff --git a/drivers/hid/hid-alps.c b/driv
From: Masaki Ota
-Delete "struct u1_dev devInfo" structure, because u1_dev structure is already
declared as "struct u1_dev *data", and this structure is used for getting U1
data in [PATCH 2/7].
Signed-off-by: Masaki Ota
---
drivers/hid/hid-alps.c | 69 +
On Thu, Oct 5, 2017 at 10:57 AM, Daniel Drake wrote:
> Hi,
>
> On the Acer laptop models Aspire ES1-533, Aspire ES1-732, PackardBell
> ENTE69AP and Gateway NE533, we are seeing a problem where the system
> immediately wakes up after being put into S3 suspend.
>
> This problem has been seen on all
On Thu, Oct 5, 2017 at 4:06 PM, Al Viro wrote:
>
> Just to make sure we are on the same page: out of kstatfs fields
> we have 5 u64 ones (see above; all of them are u64 is struct statfs64
> on all architectures), an opaque 64bit f_fsid and 5 fields that
> are long: f_type (magic numbers, all 32bit
On Tue, Oct 03, 2017 at 02:11:08PM +, Paolo Bonzini wrote:
> I'd prefer a slight change in subject and topic:
>
> --- 8<
> Subject: [PATCH] kvm/x86: Avoid async PF preempting the kernel incorrectly
>
> Currently, in PREEMPT_COUNT=n kernel, kvm_async_pf_task_wait() could call
> sc
I am Ms.Ella Golan, I am the Executive Vice President Banking Division with
FIRST INTERNATIONAL BANK OF ISRAEL LTD (FIBI).
I am getting in touch with you regarding an extremely important and urgent
matter. If you would oblige me the opportunity, I shall provide you with
details upon your response.
On 2017-09-25 16:20, Viresh Kumar wrote:
On 25-09-17, 15:51, Prasad Sodagudi wrote:
Remove the __init annotation from free_raw_capacity() to avoid
the following warning.
The function init_cpu_capacity_callback() references the
function __init free_raw_capacity().
WARNING: vmlinux.o(.text+0x425c
From: Wanpeng Li
Extract the logic of limit lapic periodic timer frequency to a new function,
this function will be used by later patches.
Cc: Paolo Bonzini
Cc: Radim Krčmář
Signed-off-by: Wanpeng Li
---
arch/x86/kvm/lapic.c | 39 ++-
1 file changed, 22 i
From: Wanpeng Li
If we take TSC-deadline mode timer out of the picture, the Intel SDM
does not say that the timer is disable when the timer mode is change,
either from one-shot to periodic or vice versa.
After this patch, the timer is no longer disarmed on change of mode, so
the counter (TMCCT)
The issue is reported in xen community.
Anthony PERARD pointed out:
https://www.mail-archive.com/xen-devel@lists.xen.org/msg117283.html#
| When developing PVH for OVMF, I've used the lapic timer. It turns out that
the
| way it is used by OVMF did not work with Xen [1]. I tried to find out how
From: Wanpeng Li
The description in the Intel SDM of how the divide configuration
register is used: "The APIC timer frequency will be the processor's bus
clock or core crystal clock frequency divided by the value specified in
the divide configuration register."
Observation of baremetal shown tha
From: Andi Kleen
Now that the xyarray stores the dimensions we can use those
to iterate over the FDs for a evsel.
Signed-off-by: Andi Kleen
---
tools/perf/builtin-stat.c | 11 +--
1 file changed, 5 insertions(+), 6 deletions(-)
diff --git a/tools/perf/builtin-stat.c b/tools/perf/built
From: Andi Kleen
perf stat can retry opening events. After opening an file descriptor
it adds the ids to the ecsel. Each event keeps a running
count of ids. When we decide to close an evsel and retry
with a different configuration this count needs to be reset,
otherwise it can overflow the buffer
On Thu, 2017-10-05 at 22:29 +0200, Michal Suchánek wrote:
> I do not expect the kernel to generate a
> stack trace every time memory allocation fails. With all the hooks in
> the code it is hard to tell, though.
All [kv].alloc failures without __GFP_NOWARN call dump_stack()
Hi Linus,
Some i915 fixes from last two weeks (as they were on a strange base
and I just waited for rc3), also a single sun4i hdmi fix.
Dave.
The following changes since commit 9e66317d3c92ddaab330c125dfe9d06eee268aff:
Linux 4.14-rc3 (2017-10-01 14:54:54 -0700)
are available in the git repos
On Thu, Oct 05, 2017 at 12:16:19PM -0400, J. Bruce Fields wrote:
> This kind of restriction sounds more like a permanent feature of the
> filesystem--something you'd set at mkfs time.
>
> We already have filesystems with these kinds of restrictions, don't we?
In general, no. Filename storage typi
Hi Kishon,
Would you review this patch set?
I checked this can apply your latest linux-phy.git / next branch (the commit id
= 415060b21f31).
Best regards,
Yoshihiro Shimoda
> -Original Message-
> From: Yoshihiro Shimoda
> Sent: Friday, September 1, 2017 11:41 AM
> To: kis...@ti.com
> Cc
On Thu, 2017-10-05 at 17:54 +0200, Sebastian Andrzej Siewior wrote:
> On 2017-10-04 18:07:59 [+0200], Mike Galbraith wrote:
> > Seems combo-patch induced some ltp posix conformance test grumbling.
> >
> > +clock_settime_8_1 ... ... FAILED
> > +clock_settime_4_2 ... ... FAILED
> > +clock_settime_
On Thu, Oct 05 2017, Matthias Kaehlcke wrote:
> Hi Neil,
>
> El Fri, Oct 06, 2017 at 10:58:59AM +1100 NeilBrown ha dit:
>
>> On Thu, Oct 05 2017, Matthias Kaehlcke wrote:
>>
>> > The raid10 driver can't be built with clang since it uses a variable
>> > length array in a structure (VLAIS):
>> >
>>
Hi All,
Based on below links __ubsan_handle_type_mismatch has been renamed to
__ubsan_handle_type_mismatch_v1.
https://github.com/llvm-mirror/compiler-rt/commit/56faee71af1888ba12ab076b3d1f9bbe223493df#diff-21369cc6f3917b27df3ced8de89cf134
https://www.mail-archive.com/gcc-bugs@gcc.gnu.org/msg
On Fri, Oct 6, 2017 at 8:16 AM, Francois Romieu wrote:
> Daniel Drake :
> [...]
>> Also, is there a standard behaviour defined for ethernet drivers
>> regarding wake-on-LAN? r8169 appears to enable wake-on-LAN by default
>> if it believes the hardware is capable of it,
>
> If so it isn't its desi
On Fri, Oct 6, 2017 at 9:24 AM, Rafael J. Wysocki wrote:
>> On the other hand, the RP05 (root port) _PRW says it will wake up the
>> system via GPE09, and the _L09 handler at least has one codepath which
>> could potentially do a Notify(PXSX, 2) to indicate an ethernet wakeup.
>
> Which can only h
Update documentation, pointer to latest tools, appoint myself as
maintainer. Given it's been unloved for so long, I don't expect anyone
will protest.
Signed-off-by: Nicolas Pitre
Tested-by: Chris Brandt
---
Documentation/filesystems/cramfs.txt | 42
MAINTAIN
Signed-off-by: Nicolas Pitre
Tested-by: Chris Brandt
---
init/do_mounts.c | 8
1 file changed, 8 insertions(+)
diff --git a/init/do_mounts.c b/init/do_mounts.c
index c2de5104aa..43b5817f60 100644
--- a/init/do_mounts.c
+++ b/init/do_mounts.c
@@ -556,6 +556,14 @@ void __init prepare_nam
This series brings a nice refresh to the cramfs filesystem, adding the
following capabilities:
- Direct memory access, bypassing the block and/or MTD layers entirely.
- Ability to store individual data blocks uncompressed.
- Ability to locate individual data blocks anywhere in the filesystem.
T
Small embedded systems typically execute the kernel code in place (XIP)
directly from flash to save on precious RAM usage. This adds the ability
to consume filesystem data directly from flash to the cramfs filesystem
as well. Cramfs is particularly well suited to this feature as it is
very simple a
Two new capabilities are introduced here:
- The ability to store some blocks uncompressed.
- The ability to locate blocks anywhere.
Those capabilities can be used independently, but the combination
opens the possibility for execute-in-place (XIP) of program text segments
that must remain uncompr
When cramfs_physmem is used then we have the opportunity to map files
directly from ROM, directly into user space, saving on RAM usage.
This gives us Execute-In-Place (XIP) support.
For a file to be mmap()-able, the map area has to correspond to a range
of uncompressed and contiguous blocks, and i
From: Masaki Ota
-Add T4 USB device Product ID. (0x1216)
-Separate T4 USB device initialization code from T4 Standard device code.
-T4 USB device is used on HP Elite x2 series
Signed-off-by: Masaki Ota
---
drivers/hid/hid-alps.c | 35 +--
drivers/hid/hid-core.c
801 - 900 of 958 matches
Mail list logo
