From: Kan Liang
Iterating all events which need to receive side-band events also bring
some overhead.
The side-band events overhead PERF_CORE_SB_OVERHEAD is a common overhead
type.
Signed-off-by: Kan Liang
---
include/linux/perf_event.h | 2 ++
From: Kan Liang
Make get_nsecs visible to collect monotonic wall time.
Introduce get_vnsecs to collect CPU time.
Signed-off-by: Kan Liang
---
tools/perf/builtin-record.c | 9 +
tools/perf/builtin-sched.c | 2 +-
tools/perf/builtin.h|
From: Kan Liang
The kernel overhead include sample overhead, multiplexing overhead and
side-band events overhead. All the information is printed in the head of
output file if the show profiling cost option is applied.
The result is sorted by CPU. If there is no available CPU
From: Kan Liang
It is used to track user space perf tool profiling time cost.
Signed-off-by: Kan Liang
---
tools/perf/util/event.c | 1 +
tools/perf/util/event.h | 5 +
tools/perf/util/session.c | 4
3 files changed, 10 insertions(+)
From: Kan Liang
Perf collects overhead information by default.
A new option --no-profile-cost-info is introduced to disable the
information collection.
Signed-off-by: Kan Liang
---
tools/include/uapi/linux/perf_event.h| 42
From: Kan Liang
Multiplexing overhead is one of the key overhead when the number of
events is more than available counters.
The multiplexing overhead PERF_CORE_MUX_OVERHEAD is a common overhead
type.
Signed-off-by: Kan Liang
---
From: Kan Liang
Outputing every overhead when it happens is very costly. The accumulated
time is more meaningful. So the overhead information should be outputted
at the very end.
The overhead information is outputted when task is scheduling out or the
event is going to be
From: Kan Liang
Profiling brings additional overhead. High overhead may impacts the
behavior of the profiling object, impacts the accuracy of the
profiling result, and even hang the system.
Currently, perf has dynamic interrupt throttle mechanism to lower the
sample rate and
Fix up these sparse warnings:
drivers/fpga/fpga-mgr.c:189:21: warning: symbol '__fpga_mgr_get' was not
declared. Should it be static?
drivers/fpga/fpga-bridge.c:30:12: warning: symbol 'bridge_list_lock' was
not declared. Should it be static?
Signed-off-by: Dinh Nguyen
---
From: Kan Liang
On x86, NMI handler is the most important part which brings overhead
for sampling. Adding a pmu specific overhead type
PERF_PMU_SAMPLE_OVERHEAD for it.
For other architectures which may don't have NMI, the overhead type can
be reused.
Signed-off-by: Kan
From: Kan Liang
Warning the user if the overhead is too high.
The overhead evaluation metrics is as below.
- Kerenl profiling cost evaluation
MAX(cpu0_overhead, cpu1_overhead,...) / perf monotonic wall time
If the rate is > 10%, a warning is printed.
- perf record
From: Kan Liang
Record the cpu time and elapsed time of perf record.
Show them in perf report.
# To display the perf.data header info, please use
--header/--header-only options.
#
#
# Elapsed time: 1199332708(ns)
# Perf record cpu time: 197780038(ns)
#
#
The following changes since commit 9c763584b7c8911106bb77af7e648bef09af9d80:
Linux 4.9-rc6 (2016-11-20 13:52:19 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git
tags/fixes-for-linus
for you to fetch changes up to
>> Problem found via lockdep:
>>
>> - lpuart_set_termios() calls del_timer_sync(>lpuart_timer) while
>> holding sport->port.lock
>>
>> - sport->lpuart_timer routine is lpuart_timer_func() that calls
>> lpuart_copy_rx_to_tty() that acquires same lock.
>>
>> To fix, move Rx DMA stopping out of
On Thu, Dec 1, 2016 at 8:22 PM, Michael Ellerman wrote:
> This adds two tests, to check that a read or write to LIST_POISON1 and
> ZERO_SIZE_PTR are blocked.
>
> The default values for both (256 and 16) typically fall in the range
> of valid user space addresses. However in
Add Northstar2 device tree entry for Broadcom Secure Processing
Unit (SPU) crypto driver.
Signed-off-by: Steve Lin
Signed-off-by: Rob Rice
---
arch/arm64/boot/dts/broadcom/ns2.dtsi | 12
1 file changed, 12 insertions(+)
diff --git
Device tree documentation for Broadcom Secure Processing Unit
(SPU) crypto driver.
Signed-off-by: Steve Lin
Signed-off-by: Rob Rice
---
.../devicetree/bindings/crypto/brcm,spu-crypto.txt | 25 ++
1 file changed, 25
Change in v2:
- select CRYPTO_DES in Kconfig
The Broadcom SPU crypto driver provides access to SPU hardware
for symmetric crypto offload. The driver supports ablkcipher,
ahash, and aead operations. The driver supports several
Broadcom SoCs with different revisions of the SPU hardware.
The driver
The CPTS drivers uses 8sec period for overflow checking with
assumption that CPTS retclk will not exceed 500MHz. But that's not
true on some TI platforms (Kesytone 2). As result, it is possible that
CPTS counter will overflow more than once between two readings.
Hence, fix it by selecting
TI CPTS IP is used as part of TI OMAP CPSW driver, but it's also
present as part of NETCP on TI Keystone 2 SoCs. So, It's required
to enable build of CPTS for both this drivers and this can be
achieved by allowing CPTS to be built separately.
Hence, allow cpts to be built separately and convert
This will provide more flexibility in changing CPTS internals and also
required for further changes.
Signed-off-by: Grygorii Strashko
---
drivers/net/ethernet/ti/cpsw.c | 28 +++-
drivers/net/ethernet/ti/cpts.h | 39
From: Murali Karicheri
The CPSW CPTS driver is capable of doing timestamping on tx/rx packets and
requires to know mult and shift factors for timestamp conversion from raw
value to nanoseconds (ptp clock). Now these mult and shift factors are
calculated manually and provided
It is preparation series intended to clean up and optimize TI CPTS driver to
facilitate further integration with other TI's SoCs like Keystone 2.
Changes in v3:
- patches reordered: fixes and small updates moved first
- added comments in code about cpts->cc_mult
- conversation range (maxsec)
There are two issues with TI CPTS code which are reproducible when TI
CPSW ethX device passes few up/down iterations:
- cpts refclk prepare counter continuously incremented after each
up/down iteration;
- devm_clk_get(dev, "cpts") is called many times.
Hence, fix these issues by using
Switch to readl/writel_relaxed() APIs, because this is recommended
API and the CPTS IP is reused on Keystone 2 SoCs
where LE/BE modes are supported.
Acked-by: Richard Cochran
Signed-off-by: Grygorii Strashko
---
drivers/net/ethernet/ti/cpts.c
The cpts now is left enabled after unregistration.
Hence, disable it in cpts_unregister().
Acked-by: Richard Cochran
Signed-off-by: Grygorii Strashko
---
drivers/net/ethernet/ti/cpts.c | 4
1 file changed, 4 insertions(+)
diff --git
Move DT properties parsing into CPTS driver to simplify CPSW
code and CPTS driver porting on other SoC in the future
(like Keystone 2) - with this change it will not be required
to add the same DT parsing code in Keystone 2 NETCP driver.
Signed-off-by: Grygorii Strashko
The cyclecounter mult and shift values can be calculated based on the
CPTS rfclk frequency and timekeepnig framework provides required algos
and API's.
Hence, calc mult and shift basing on CPTS rfclk frequency if both
cpts_clock_shift and cpts_clock_mult properties are not provided in DT (the
CPTS module and IRQs are always enabled when CPTS is registered,
before starting overflow check work, and disabled during
deregistration, when overflow check work has been canceled already.
So, It doesn't require to (re)enable CPTS module and IRQs in
cpts_overflow_check().
Acked-by: Richard
From: WingMan Kwok
When a CPTS user does not exit gracefully by disabling cpts
timestamping and leaving a joined multicast group, the system
continues to receive and timestamps the ptp packets which eventually
occupy all the event list entries. When this happns, the added code
The ptp clock registered before spinlock, which is protecting it, and
before timecounter and cyclecounter initialization in cpts_register().
So, ensure that ptp clock is registered the last, after everything
else is done.
Acked-by: Richard Cochran
Signed-off-by:
The current implementation CPTS initialization and deinitialization
(represented by cpts_register/unregister()) does too many static
initialization from .ndo_open(), which is reasonable to do once at probe
time instead, and also require caller to allocate memory for struct cpts,
which is internal
ADC channel 0 photodiode detects both infrared + visible light,
but ADC channel 1 just detects infrared. However, the latter is a bit
more sensitive in that range so complete darkness or low light causes
a error condition in which the chan0 - chan1 is negative that
results in a -EAGAIN.
This
On Fri, Dec 2, 2016 at 11:35 AM, Linus Torvalds
wrote:
> On Fri, Dec 2, 2016 at 11:30 AM, Andy Lutomirski wrote:
>>
>> How's this?
>
> Looks ok. I do think that
>
>> I suppose it could be an unconditional IRET-to-self, but that's a good
>> deal
On 12/02/2016 03:50 AM, Bhumika Goyal wrote:
The structures rate_control_ops are only passed as an argument to the
functions ieee80211_rate_control_{register/unregister}. This argument is
of type const, so rate_control_ops having this property can also be
declared as const.
Done using
On Fri, Dec 2, 2016 at 11:20 AM, Fabian Frederick wrote:
> There's no need to warn on persistence yet as some validity tests
> are on the way.
>
> Signed-off-by: Fabian Frederick
> ---
> drivers/nvdimm/pmem.c | 6 +++---
> 1 file changed, 3 insertions(+), 3
On Fri, Dec 2, 2016 at 11:20 AM, Fabian Frederick wrote:
> Signed-off-by: Fabian Frederick
> ---
> drivers/nvdimm/pmem.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/nvdimm/pmem.c b/drivers/nvdimm/pmem.c
> index
On Fri 2016-12-02 19:48:40, Dmitry Vyukov wrote:
> Hello,
>
> There was an issue discussed a year ago which leads to
> unkillalble/unwaitable zombie processes due to PTRACE_TRACEME:
> https://groups.google.com/d/msg/syzkaller/uGzwvhlCXAw/E-cfY2ejAgAJ
> and I though it has been fixed by
On 12/02/2016 10:47 AM, Tony Lindgren wrote:
* Grygorii Strashko [161129 08:43]:
On 11/24/2016 12:19 AM, Keerthy wrote:
From: Grygorii Strashko
Now ARM Global timer (rating 300) will not be selected as clocksource,
because it's
On 12/02/2016 06:44 AM, Andrew Cooper wrote:
> On 02/12/16 00:35, Andy Lutomirski wrote:
>> On Xen PV, CPUID is likely to trap, and Xen hypercalls aren't
>> guaranteed to serialize. (Even CPUID isn't *really* guaranteed to
>> serialize on Xen PV, but, in practice, any trap it generates will
>>
On Tue, 29 Nov 2016 10:39:39 -0600
Eric Van Hensbergen wrote:
> Any idea of what xfstests is doing at this point in time? I'd be a
> bit worried about some sort of loop in the namespace since it seems to
> be in path traversal. Could also be some sort of resource leak or
>
On Thu, 1 Dec 2016, Paul Bolle wrote:
> On Thu, 2016-12-01 at 12:42 -0500, Nicolas Pitre wrote:
> > OK I understand what the problem is. However most of those hunks below
> > are definitely wrong. ;-)
>
> Probably. By now I've narrowed it down to just these two hunks:
And they're both wrong.
On Wed, Nov 30, 2016 at 11:00:30PM -0500, Len Brown wrote:
> From: Len Brown
>
> Based on a recent session at the Linux Plumber's Conference,
> we need to be more clear about how a BIOS should use _OSI
> to properly support Linux.
>
> Signed-off-by: Len Brown
On Fri, Dec 2, 2016 at 11:20 AM, Fabian Frederick wrote:
> add cleared_sectors variable to add more readability.
>
> Signed-off-by: Fabian Frederick
> ---
> drivers/nvdimm/pmem.c | 12 ++--
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git
Since this discussion affects which keys can be added to trusted
keyrings, cc'ing linux-ima-devel.
On Fri, 2016-12-02 at 10:57 -0800, James Bottomley wrote:
> On Thu, 2016-11-24 at 11:17 -0800, James Bottomley wrote:
> > On Mon, 2016-11-21 at 16:16 +, Ard Biesheuvel wrote:
> > > On 16
On Wed, Nov 30, 2016 at 7:15 PM, Luis R. Rodriguez wrote:
> BTW the test driver lib/test_linktables/test-linktables.c seems to
> fail on ppc at run time at:
>
> rc = trigger_config_run_named(test_dev, ".text");
>
> I'm having issues getting a ppc / ppc64 box going to easily
From: Gregory CLEMENT
Date: Thu, 1 Dec 2016 18:03:03 +0100
> The Armada 37xx is a new ARMv8 SoC from Marvell using same network
> controller as the older Armada 370/38x/XP SoCs. This series adapts the
> driver in order to be able to use it on this new SoC.
On Wed, Nov 30, 2016 at 5:49 PM, Linus Walleij wrote:
> On Sun, Nov 27, 2016 at 11:51 AM, Jonathan Cameron wrote:
>> On 26/11/16 03:47, Aniroop Mathur wrote:
>
> [bmp280.c]
>
>>> /* Wait to make sure we started up properly */
>>> -
Added support APIs for IB core to register/unregister every IB/RDMA
device with rdma cgroup for tracking rdma resources.
IB core registers with rdma cgroup controller.
Added support APIs for uverbs layer to make use of rdma controller.
Added uverbs layer to perform resource charge/uncharge
Added documentation for v1 and v2 version describing high
level design and usage examples on using rdma controller.
Signed-off-by: Parav Pandit
---
Documentation/cgroup-v1/rdma.txt | 109 +++
Documentation/cgroup-v2.txt | 38
On Fri, Dec 2, 2016 at 11:20 AM, Borislav Petkov wrote:
>
> Something like below?
The optimize-nops thing needs it too, I think.
Again, this will never matter in practice (even if somebody has a i486
s till, the prefetch window size is like 16 bytes or something), but
from a
On Fri, Dec 02, 2016 at 11:24:09AM -0800, Linus Torvalds wrote:
> The optimize-nops thing needs it too, I think.
Ah, it is called only from apply_alternatives() but sure, it is safer
this way. Lemme do that and run it through the boxes to see whether
anything catches fire.
> Again, this will
On Fri, Dec 02, 2016 at 11:23:09AM -0800, Andy Lutomirski wrote:
> Not even firmware loading wants it. Firmware loading needs
Microcode...
> specifically cpuid(eax=1). It has nothing to do with serializing
... but yes, of course. NOT sync_core() but CPUID(1).
Thanks!
--
Regards/Gruss,
On 12/1/2016 5:28 PM, yunhong jiang wrote:
Hi, Chris
I noticed your task isolation patch set at
https://lkml.org/lkml/2016/8/9/759 . Thanks a lot for the great effort.
I checked the patch and have some questions about how to use this
functionality on the NFV environment. In the NFV
On Fri, Dec 2, 2016 at 12:11 AM, Jon Masters wrote:
> You're welcome.
>
> (Unrelated) Note that I added a console= and earlycon in my test (and got the
> baud rate wrong for the console but nevermind...was ssh'd in after the
> earlycon output I cared about anyway) because of
On 12/02/2016 05:28 AM, Ivan Khoronzhuk wrote:
> On Thu, Dec 01, 2016 at 05:34:30PM -0600, Grygorii Strashko wrote:
>> Add optional property "descs_pool_size" to specify buffer descriptor's
>> pool size. The "descs_pool_size" should define total number of CPDMA
>> CPPI descriptors to be used for
From: Ben Evans
Remove all obdo related functions from lustre_idl.h
Create lustre_odbo.h. Include where appropriate.
Make the functions lustre_get_wire_obdo and
lustre_set_wire_obdo to not be inlined functions.
Signed-off-by: Ben Evans
Intel-bug-id:
From: Ben Evans
It was found if you sort the headers alphabetically
that it reduced patch conflicts. This patch sorts
the headers alphabetically and also place linux
header first, then uapi header and finally the
lustre kernel headers.
Signed-off-by: Ben Evans
Hi,
On 02-12-16 15:22, Icenowy Zheng wrote:
01.12.2016, 17:36, "Maxime Ripard" :
On Mon, Nov 28, 2016 at 12:29:07AM +, André Przywara wrote:
> Something more interesting happened.
>
> Xunlong made a add-on board for Orange Pi Zero, which exposes the
2016-12-02 14:59 GMT+01:00 Lee Jones :
> On Fri, 02 Dec 2016, Benjamin Gaignard wrote:
>
>> Define bindings for stm32 timer trigger
>>
>> version 3:
>> - change file name
>> - add cross reference with mfd bindings
>>
>> version 2:
>> - only keep one compatible
>> - add DT
The datasheet states:
"If the MODE field selects an 8-bit frame then this [parity error] bit
is undefined. Software should ignore this bit when reading 8-bit frames."
Signed-off-by: Lee Jones
---
drivers/tty/serial/st-asc.c | 16 +---
1 file changed, 13
According to the documentation, the PHYs supported by this driver
can also support pause frames. Announce this to be so.
Tested with a TI83822I.
Acked-by: Andrew F. Davis
Signed-off-by: Jesper Nilsson
---
drivers/net/phy/dp83848.c | 4 +++-
1 file changed,
On Fri, Dec 2, 2016 at 9:44 AM, Michal Hocko wrote:
> On Fri 02-12-16 15:38:48, Michal Hocko wrote:
>> On Fri 02-12-16 09:24:35, Dan Streetman wrote:
>> > On Fri, Dec 2, 2016 at 8:46 AM, Michal Hocko wrote:
>> > > On Wed 30-11-16 13:15:16, Yu Zhao wrote:
>>
Currently the driver sets all the device transactions privileges
to UNPRIVILEGED, but there are cases where the iommu masters wants
to isolate privileged supervisor and unprivileged user.
So don't override the privileged setting to unprivileged, instead
set it to default as incoming and let it be
From: Mitchel Humpherys
The PL330 performs privileged instruction fetches. This can result in
SMMU permission faults on SMMUs that implement the ARMv8 VMSA, which
specifies that mappings that are writeable at one execution level shall
not be executable at any
From: Colin Ian King
allocates string 'new' is not free'd on the exit path when
cdm_element_count <= 0. Fix this by kfree'ing it.
Fixes CoverityScan CID#1375923 "Resource Leak"
Signed-off-by: Colin Ian King
---
Signed-off-by: Nathan Sullivan
---
This is required by "gpio: mmio: add support for NI 169445 NAND GPIO"
Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/vendor-prefixes.txt
While trying to set the pll0 rate from the kernel I noticed there are
two issues with da850 clocks. The first patch fixes an infinite loop
in propagate_rate(). The third fixes an oops in da850_set_pll0rate().
The second patch is just a coding style fix, while we're at it.
v1 -> v2:
- change the
> -Original Message-
> From: Greg KH [mailto:gre...@linuxfoundation.org]
> Sent: Thursday, December 1, 2016 11:36 PM
> To: KY Srinivasan
> Cc: linux-kernel@vger.kernel.org; de...@linuxdriverproject.org;
> o...@aepfle.de; a...@canonical.com; vkuzn...@redhat.com;
>
Hi Thierry,
On Fri, Dec 2, 2016 at 7:35 AM, Thierry Escande
wrote:
> Hi Benson,
>
> This series adds support for the LPC Microchip Embedded Controller 1322.
Thanks. I'll queue these up for the first batch of changes I'll work
on as chrome platform maintainer.
>
>
> On 02.12.2016, at 09:19, Eric Biggers wrote:
>
> On Thu, Dec 01, 2016 at 11:14:55PM +0100, Richard Weinberger wrote:
>> + * @lblk_num: Logical block number. This must be unique for multiple
>> + * calls with same page.
>
> Must be unique for all calls with
Hi Pavel
On 12/2/2016 11:42 AM, Pavel Machek wrote:
Hi!
Anyway... since you asked. I belive I have way to disable NAPI / tx
coalescing in the driver. Unfortunately, locking is missing on the rx
path, and needs to be extended to _irqsave variant on tx path.
I have just replied to a previous
On Fri, Dec 02, 2016 at 03:38:51PM +, KY Srinivasan wrote:
>
>
> > -Original Message-
> > From: Greg KH [mailto:gre...@linuxfoundation.org]
> > Sent: Thursday, December 1, 2016 11:36 PM
> > To: KY Srinivasan
> > Cc: linux-kernel@vger.kernel.org;
From: Michal Kubecek
Date: Fri, 2 Dec 2016 09:33:41 +0100 (CET)
> Qian Zhang (张谦) reported a potential socket buffer overflow in
> tipc_msg_build() which is also known as CVE-2016-8632: due to
> insufficient checks, a buffer overflow can occur if MTU is too short for
> even
On Fri, Dec 2, 2016 at 10:50 AM, Borislav Petkov wrote:
>
> Right, we can try to do something like invalidate_icache() or so in
> there with the JMP so that the BSP refetches modified code and see where
> it gets us.
I'd really rather rjust mark it noinline with a comment. That
On Thu, 2016-11-24 at 11:17 -0800, James Bottomley wrote:
> On Mon, 2016-11-21 at 16:16 +, Ard Biesheuvel wrote:
> > On 16 November 2016 at 18:11, David Howells
> > wrote:
> > > From: Josh Boyer
> > >
> > > Secure Boot stores a list of allowed
On Wed, Nov 30, 2016 at 8:13 PM, Aniroop Mathur wrote:
> On 30 Nov 2016 19:05, "Lars-Peter Clausen" wrote:
> >
> > On 11/27/2016 11:51 AM, Jonathan Cameron wrote:
> > > On 26/11/16 03:47, Aniroop Mathur wrote:
> > >> msleep(1~20) may not do what the
Patch is generated and tested against below Doug's linux-rdma
git tree.
URL: git://git.kernel.org/pub/scm/linux/kernel/git/dledford/rdma.git
Branch: master
Patchset is also compiled and tested against below Tejun's cgroup tree
using cgroup v2 mode.
URL:
Added rdma cgroup controller that does accounting, limit enforcement
on rdma/IB resources.
Added rdma cgroup header file which defines its APIs to perform
charing/uncharing functionality. It also defined APIs for RDMA/IB
stack for device registration. Devices which are registered will
participate
kernel command lines like memmap=1M!512M gave no pmem outputs
without debugging.
Signed-off-by: Fabian Frederick
---
drivers/nvdimm/namespace_devs.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/nvdimm/namespace_devs.c
Signed-off-by: Fabian Frederick
---
drivers/nvdimm/pmem.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/nvdimm/pmem.c b/drivers/nvdimm/pmem.c
index 2461843..822a712 100644
--- a/drivers/nvdimm/pmem.c
+++ b/drivers/nvdimm/pmem.c
@@ -267,7 +267,7 @@
There's no need to warn on persistence yet as some validity tests
are on the way.
Signed-off-by: Fabian Frederick
---
drivers/nvdimm/pmem.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/nvdimm/pmem.c b/drivers/nvdimm/pmem.c
index
add cleared_sectors variable to add more readability.
Signed-off-by: Fabian Frederick
---
drivers/nvdimm/pmem.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/nvdimm/pmem.c b/drivers/nvdimm/pmem.c
index 204912c..4da4735 100644
---
On Fri, Dec 02, 2016 at 11:03:50AM -0800, Linus Torvalds wrote:
> I'd really rather rjust mark it noinline with a comment. That way the
> return from the function acts as the control flow change.
Something like below?
It boots in a guest but that doesn't mean anything.
> 'sync_core()' doesn't
else after return is not needed.
Signed-off-by: Fabian Frederick
---
drivers/nvdimm/claim.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/drivers/nvdimm/claim.c b/drivers/nvdimm/claim.c
index d5dc80c..c0c113e 100644
--- a/drivers/nvdimm/claim.c
+++
Hi folks!
I'm sorry to bother you, guys, but neither the mailing list
'kpreempt-t...@lists.sourceforge.net' nor Robert's address
'r...@tech9.net' exist anymore.
If I have to address someone else, pls let me know.
We're currently investigating the locking of data structures in the
Linux Kernel
On Thu, 1 Dec 2016, Guenter Roeck wrote:
> On a system with a defective USB device connected to an USB hub,
> an endless sequence of port connect events was observed. The sequence
> of events as observed is as follows:
>
> - Port reports connected event (port status=USB_PORT_STAT_CONNECTION).
>
On Fri, Dec 2, 2016 at 11:30 AM, Andy Lutomirski wrote:
>
> How's this?
Looks ok. I do think that
> I suppose it could be an unconditional IRET-to-self, but that's a good
> deal slower and not a whole lot simpler. Although if we start doing
> it right, performance won't
This patch fixes a checkpatch warning.
Signed-off-by: Fernando Apesteguia
---
drivers/staging/dgnc/dgnc_tty.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/dgnc/dgnc_tty.h b/drivers/staging/dgnc/dgnc_tty.h
index
On 11/10/2016 04:02 AM, Matt Redfearn wrote:
> When relocatable support for MIPS was merged, there was no support for
> an architecture to add a postlink step for vmlinux. This meant that only
> invoking a target within the boot directory, such as uImage, caused the
> relocations to be inserted
From: Ben Evans
It was found if you sort the headers alphabetically
that it reduced patch conflicts. This patch sorts
the headers alphabetically and also place linux
header first, then uapi header and finally the
lustre kernel headers.
Signed-off-by: Ben Evans
LAPIC after reset is in xAPIC mode, which poses a problem for hotplug of
VCPUs with high APIC ID, because reset VCPU is waiting for INIT/SIPI,
but there is no way to uniquely address it using xAPIC.
>From many possible options, we chose the one that also works on real
hardware: accepting
Slow path tried to prevent IPIs from x2APIC VCPUs from being delivered
to xAPIC VCPUs and vice-versa. Make slow path behave like fast path,
which never distinguished that.
Signed-off-by: Radim Krčmář
---
arch/x86/kvm/lapic.c | 14 ++
1 file changed, 6
From: Ben Evans
Migrate functions set/get_mrc_cr_flags, ldlm_res_eq
ldlm_extent_overlap, ldlm_extent_contain,
ldlm_request_bufsize, and alll the PTLRPC dump_*
functions out of lustre_idl.h which is a UAPI header
to the places in the kernel code they are actually used.
Delete
In order for lustre_idl.h to be usable for both user
land and kernel space it has to use the proper
byteorder functions.
Signed-off-by: James Simmons
Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-6245
Reviewed-on: http://review.whamcloud.com/16916
Reviewed-by: Frank
From: Ben Evans
Create headers for pack_generic.c and llog_swab.c
Reference only where needed. This separates out
the kernel only code from lustre_idl.h that is
an UAPI header.
Signed-off-by: Ben Evans
Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-6401
The problem is described in [4/4].
[1/4] is a prerequisite to allow a cleanup in [2/4].
[2/4] hopefully makes [4/4] easier to understand.
[3/4] fixes mistakes from dealing with the mixed mode.
[4/4] allows the hotplug and and add a capability for it.
Radim Krčmář (4):
KVM: x86: use delivery
There were three calls sites:
- recalculate_apic_map and kvm_apic_match_physical_addr, where it would
only complicate implementation of x2APIC hotplug;
- in apic_debug, where it was still somewhat preserved, but keeping the
old function just for apic_debug was not worth it
Signed-off-by:
The header lustre_idl.h is a UAPI header which contains extras
that don't belong. This patch set moves a bunch of very kernel
specific material out of the header. Lastly proper byteorder
functions are used so this file can build in user space as well.
Ben Evans (5):
staging: lustre: headers:
On 12/02/2016 12:52 PM, h...@zytor.com wrote:
> On December 2, 2016 8:08:55 AM PST, Ingo Molnar wrote:
>> * Boris Ostrovsky wrote:
>>
>>> On 12/02/2016 04:45 AM, Ingo Molnar wrote:
* Boris Ostrovsky wrote:
>
501 - 600 of 1302 matches
Mail list logo