There was no architecture we had to increase NCCS on,
so the size of struct termios did not change.
Signed-off-by: Arseny Maslennikov
---
arch/alpha/include/asm/termios.h | 4 ++--
arch/alpha/include/uapi/asm/termbits.h | 1 +
arch/ia64/include/asm/termios.h | 4 ++--
This complementary patch defines SIGINFO as a synonym for SIGPWR
on every architecture supported by the kernel.
The particular signal number chosen does not really matter and is only
required for the related tty functionality to work properly,
so if it does not suite expectations, any suggestions
This patch series introduces TTY keyboard status request, a feature of
the n_tty line discipline that reserves a character in struct termios
(^T by default) and reacts to it by printing a short informational line
to the terminal and sending a Unix signal to the tty's foreground
process group. The
Signed-off-by: Arseny Maslennikov
---
arch/alpha/include/uapi/asm/termbits.h | 1 +
arch/ia64/include/uapi/asm/termbits.h| 1 +
arch/mips/include/uapi/asm/termbits.h| 1 +
arch/parisc/include/uapi/asm/termbits.h | 1 +
arch/powerpc/include/uapi/asm/termbits.h | 1 +
No kerninfo line is printed yet.
No existing implementation of this on any Unix-like system echoes
the status character; no existing implementation discards or flushes
pending input on VSTATUS receipt.
There are existing popular TUI applications (e. g. mutt) that only
turn off icanon and not
This matches the behaviour of other Unix-like systems that have SIGINFO
and causes less harm to processes that do not install handlers for this
signal, making the keyboard status character non-fatal for them.
This is implemented with the assumption that SIGINFO is defined
to be equivalent to
To simplify internal re-use of the line discipline's write method,
we isolate the work it does to its own function.
Since in-kernel callers might not refer to the tty through a file,
the struct file* argument might make no sense, so we also stop
tty_io_nonblock() from dereferencing file too
On Sun, Jun 2, 2019 at 7:25 PM Emanuel Bennici
wrote:
>
> Fix checkpatch.pl 'line over 80 characters' Warning in ibmphp_ebda.c and
> ibmphp_hpc.c
I'm not sure it's needed.
And actually some of the changes are the regressions in order of
readability ratio.
> +
Hi Trond,
I have been noticing intermittent failures with a system suspend test on
some of our machines that have a NFS mounted root file-system. Bisecting
this issue points to your commit 431235818bc3 ("SUNRPC: Declare RPC
timers as TIMER_DEFERRABLE") and reverting this on top of v5.2-rc3 does
On Sun, Jun 2, 2019 at 7:35 PM Emanuel Bennici
wrote:
>
> The 'Exit' Debug message is superfluous ftrace can be used instead.
>
When reviewer gives you a comment in one entry, your job is to check
your entire series and address the same comment in other places.
There are many such unneeded debug
From: Peter Ujfalusi
J721E SoCs have same I2C IP as OMAP SoCs. Add new compatible to
handle J721E SoCs.
Signed-off-by: Peter Ujfalusi
Signed-off-by: Vignesh Raghavendra
---
Initial support for J721E Platform is proposed here:
https://lore.kernel.org/patchwork/cover/1077382/
On Wed, May 29, 2019 at 10:44 AM Chunfeng Yun wrote:
>
> Due to the requirement of usb-connector.txt binding, the old way
> using extcon to support USB Dual-Role switch is now deprecated
> when use Type-B connector.
> This patch introduces a driver of Type-B connector which typically
> uses an
On Wed, 05 Jun 2019, Johan Hovold wrote:
> On Wed, Jun 05, 2019 at 09:20:47AM +0100, Lee Jones wrote:
> > On Wed, 05 Jun 2019, Johan Hovold wrote:
>
> > > No, we don't add noise like this to the logs just because it may be
> > > useful while debugging. Even one-liners add up.
> >
> > One line
On Wed, Jun 05, 2019 at 03:50:31PM +0800, Chunfeng Yun wrote:
> On Tue, 2019-06-04 at 13:59 +0200, Greg Kroah-Hartman wrote:
> > On Tue, Jun 04, 2019 at 11:32:58AM +0200, Greg Kroah-Hartman wrote:
> > > The USB gadget subsystem wants to use the USB debugfs root directory, so
> > > move it to the
在 2019/6/4 23:24, Eric Dumazet 写道:
> On Tue, Jun 4, 2019 at 7:47 AM Mao Wenan wrote:
>>
>> There is one issue about bonding mode BOND_MODE_BROADCAST, and
>> two slaves with diffierent affinity, so packets will be handled
>> by different cpu. These are two pre-conditions in this case.
>>
On Wed, Jun 05, 2019 at 09:49:21AM +0100, Lee Jones wrote:
> On Wed, 05 Jun 2019, Johan Hovold wrote:
>
> > On Wed, Jun 05, 2019 at 09:20:47AM +0100, Lee Jones wrote:
> > > On Wed, 05 Jun 2019, Johan Hovold wrote:
> > > > There are plenty of options for debugging already ranging from adding a
>
On 06/04, Linus Torvalds wrote:
>
> On Tue, Jun 4, 2019 at 6:41 AM Oleg Nesterov wrote:
> >
> > This is the minimal fix for stable, I'll send cleanups later.
>
> Ugh. I htink this is correct, but I wish we had a better and more
> intuitive interface.
Yes,
> In particular, since
Hi all, this is Philip who maintains the 0-Day CI test service.
Thanks for anyone who subscribing to the service. We will have a
major lab construction during next few days, thus need to pause
the service until Jun 11. Sorry for any inconvenience caused by
this, we will try our best to have it
On Mon, 6 May 2019 at 15:00, Marek Szyprowski wrote:
>
> Samsung Exynos SoCs require to force UTMI width to 8bit, otherwise the
> host side of the shared USB2 PHY doesn't work.
>
> Reported-by: Krzysztof Kozlowski
> Fixes: 707d80f0a3c5 ("usb: dwc2: gadget: Replace phyif with phy_utmi_width")
>
>> /*
>> * For now, we have a linear search to go find the appropriate
>> * memory_block corresponding to a particular phys_index. If
>> @@ -658,6 +670,11 @@ static int init_memory_block(struct memory_block
>> **memory, int block_id,
>> unsigned long start_pfn;
>> int ret = 0;
>>
>> +
On Wed, 2019-06-05 at 11:41 +0300, Andy Shevchenko wrote:
> On Sun, Jun 2, 2019 at 7:25 PM Emanuel Bennici
> wrote:
[]
> > + debug("%s - call process_changeinstatus for"
> > + "slot[%d]\n", __func__, i);
>
> Do not split string
On 05.06.19 00:07, Wei Yang wrote:
> On Mon, May 27, 2019 at 01:11:50PM +0200, David Hildenbrand wrote:
>> Let's factor out removing of memory block devices, which is only
>> necessary for memory added via add_memory() and friends that created
>> memory block devices. Remove the devices before
On Wed, Jun 5, 2019 at 4:36 PM Catalin Marinas wrote:
>
> On Mon, May 27, 2019 at 05:34:10PM +0900, Masahiro Yamada wrote:
> > Some in-kernel headers use _BITUL() instead of BIT().
> >
> > arch/arm64/include/asm/sysreg.h
> > arch/s390/include/asm/*.h
> >
> > I think the reason is because BIT()
Locking is not needed for the phy_g12a_usb3_pcie_cr_bus_read/write() and
currently it causes the following BUG because of the usage of the
regmap_read_poll_timeout() running in spinlock_irq, configured by regmap
fast_io.
Simply disable locking in the cr_regmap config since it's only used from
From: Linus Torvalds
> Sent: 04 June 2019 22:27
> Ugh. I htink this is correct, but I wish we had a better and more
> intuitive interface.
>
> In particular, since restore_user_sigmask() basically wants to check
> for "signal_pending()" anyway (to decide if the mask should be
> restored by signal
On Tue, May 28, 2019 at 05:57:44AM -0700, Angus Ainslie (Purism) wrote:
> The Librem5 devkit is based on the imx8mq from NXP. This is a default
> devicetree to boot the board to a command prompt.
>
> Changes since v14:
>
> Add regulator-always-on for the SNVS regulators.
> Added pgc nodes.
>
On 06/04, Eric W. Biederman wrote:
>
> >> - restore_user_sigmask(ksig.sigmask, );
> >> - if (signal_pending(current) && !ret)
> >> +
> >> + interrupted = signal_pending(current);
> >> + restore_user_sigmask(ksig.sigmask, , interrupted);
> >> + if (interrupted && !ret)
On Tue, May 28, 2019 at 09:11:01AM -0700, Angus Ainslie (Purism) wrote:
> Add a node for the snvs power key, "disabled" by default.
>
> Signed-off-by: Angus Ainslie (Purism)
Applied, thanks.
From: Spyridon Papageorgiou
When a USB device fails to enumerate, only a kernel message is printed.
With this patch, a uevent is also generated to notify userspace.
Services can monitor for the event through udev and handle failures
accordingly.
The "port_enumerate_fail_notify()" function name
On Tue, Jun 04, 2019 at 03:50:40PM -0700, kan.li...@linux.intel.com wrote:
> From: Kan Liang
>
> There is no function to retrieve die id information of a given CPU.
>
> Add cpu_map__get_die_id() to retrieve die id information.
>
> Signed-off-by: Kan Liang
> ---
>
> No changes since V2.
As for FOLL_LONGTERM, it is checked in the slow path
__gup_longterm_unlocked(). But it is not checked in the fast path, which
means a possible leak of CMA page to longterm pinned requirement through
this crack.
Place a check in the fast path.
Signed-off-by: Pingfan Liu
Cc: Ira Weiny
Cc: Andrew
To better reflect the held state of pages and make code self-explaining,
rename nr as nr_pinned.
Signed-off-by: Pingfan Liu
Cc: Ira Weiny
Cc: Andrew Morton
Cc: Mike Rapoport
Cc: Dan Williams
Cc: Matthew Wilcox
Cc: John Hubbard
Cc: "Aneesh Kumar K.V"
Cc: Keith Busch
Cc: Christoph Hellwig
On Tue, 2019-06-04 at 17:00 -0700, Eric Anholt wrote:
> Nicolas Saenz Julienne writes:
>
> > Registers clk-raspberrypi as a platform device as part of the driver's
> > probe sequence.
>
> Similar to how we have VCHI register platform devices for the services
> VCHI provides, shouldn't we have
Hi Eric,
On Tue, 2019-06-04 at 17:18 -0700, Eric Anholt wrote:
> Nicolas Saenz Julienne writes:
>
> > Raspberry Pi's firmware offers and interface though which update it's
> > performance requirements. It allows us to request for specific runtime
> > frequencies, which the firmware might or
The patch changes the way how the 'ops' gets populated for different
device versions. The matching function now uses 'of_device_id' in order
to identify the device type.
Signed-off-by: Lukasz Luba
Signed-off-by: Chanwoo Choi
---
drivers/devfreq/event/exynos-ppmu.c | 38
This patch adds posibility to choose what type of data should be counted
by the PPMU counter. Now the type comes from DT where the event has been
defined. When there is no 'event-data-type' the default value is used,
which is 'read+write data in bytes'.
It is needed when you want to know not only
Greetings,
I humbly solicit for your partnership to transfer €15 million Euros
into your personal or company’s account .Contact me for more detailed
explanation.
Kindly send me the followings
Full Names
Address
Occupation
Direct Mobile Telephone Lines
Nationality
Ahmed Zama
+22675844869
The patch adds new field in the PPMU event which shows explicitly
what kind of data the event is monitoring. It is possible to change it
using defined values in exynos_ppmu.h file.
Acked-by: Chanwoo Choi
Signed-off-by: Lukasz Luba
---
arch/arm/boot/dts/exynos4412-ppmu-common.dtsi | 10
Extend the documenation by events description with new 'event-data-type'
field. Add example how the event might be defined in DT.
Signed-off-by: Lukasz Luba
Signed-off-by: Chanwoo Choi
---
.../bindings/devfreq/event/exynos-ppmu.txt| 26 +--
1 file changed, 24 insertions(+),
This patch add support of a new feature which can be used in DT:
Performance Monitoring Unit with defined event data type.
In this patch the event data types are defined for Exynos PPMU.
The patch also updates the MAINTAINERS file accordingly and
adds the header file to devfreq event subsystem.
Hi all,
This patch set extends PPMU on Samsung Exynos by choosing type of data
which shell be counter in the PPMU registers.
It is possible to count e.g. read or write requests, read or write data
or latency.
A new field has been added in the DT 'event' node called 'event-data-type'.
It is them
Hi,
this warning turned up on s390:
[7.041512] [ cut here ]
[7.041518] DMA-API: nvme :00:00.0: mapping sg segment longer than
device claims to support [len=106496] [max=65536]
[7.041531] WARNING: CPU: 1 PID: 229 at kernel/dma/debug.c:1233
On Wed, 5 Jun 2019 at 06:23, David Miller wrote:
>
> From: Vladimir Oltean
> Date: Tue, 4 Jun 2019 20:07:39 +0300
>
> > This patchset adds the following:
> >
> > - A timecounter/cyclecounter based PHC for the free-running
> >timestamping clock of this switch.
> >
> > - A state machine
Hi Brian,
> (1) iterating / clearing the mwifiex reordering table
> (2) dispatching received packets to upper layers
>
> This makes it much harder to make lock recursion mistakes, as these two
> steps no longer need to hold the same locks.
Yes, this is clean;
>
> Testing: I've played with a
Hi Viresh,
On Tuesday 04 Jun 2019 at 12:31:52 (+0530), Viresh Kumar wrote:
> The same formula to check utilization against capacity (after
> considering capacity_margin) is already used at 5 different locations.
>
> This patch creates a new macro, fits_capacity(), which can be used from
> all
On Wed, May 29, 2019 at 02:50:56PM +0800, anson.hu...@nxp.com wrote:
> From: Anson Huang
>
> On i.MX7D SDB board, SW2 supplies a lot of peripheral devices,
> its voltage should be fixed at 1.8V. The commit 43967d9b5a7c
> ("ARM: dts: imx7d-sdb: Assign corresponding power supply for LDOs")
>
> -Original Message-
> From: Zhenyu Wang [mailto:zhen...@linux.intel.com]
> Sent: Wednesday, June 5, 2019 12:05 PM
> To: Zhang, Tina
> Cc: intel-gvt-...@lists.freedesktop.org; k...@vger.kernel.org; linux-
> ker...@vger.kernel.org; kra...@redhat.com; zhen...@linux.intel.com; Lv,
>
Hi Randy,
Thanks for your help. But it seems I've already made the same fixup for the
problem in
http://lists.infradead.org/pipermail/linux-mediatek/2019-June/020301.html
as soon as the kbuild test robot reported this.
Sean
On Tue, 2019-06-04 at 22:52 -0700, Randy Dunlap wrote:
>
On Tue, May 28, 2019 at 11:59:48PM -0700, Andrey Smirnov wrote:
> Since this driver already handles changer detction state, copy the
> workaround code currently residing in arch/arm/mach-imx/anatop.c into
> this drier to consolidate the places modifying it.
>
> Signed-off-by: Andrey Smirnov
>
On Wed, 5 Jun 2019 at 06:41, Coly Li wrote:
>
> On 2019/6/5 1:24 上午, Bjørn Forsman wrote:
> > On Tue, 4 Jun 2019 at 17:41, Coly Li wrote:
> >>
> >> On 2019/6/4 10:59 下午, Coly Li wrote:
> >>> On 2019/6/4 7:00 下午, Bjørn Forsman wrote:
> Hi all,
>
> I get a kernel oops from bcache
On 06/05, David Laight wrote:
>
> epoll() would have:
> if (restore_user_sigmask(xxx.sigmask, , !ret || ret == -EINTR))
> ret = -EINTR;
I don't think so but lets discuss this later.
> I also think it could be simplified if code that loaded the 'user sigmask'
> saved the old
Hi Shimoda-san,
On Wed, Jun 5, 2019 at 6:54 AM Yoshihiro Shimoda
wrote:
> The powered flag should be set for any other phys anyway. Otherwise,
> after we have revised the device tree for the usb phy, the following
> warning happened during a second system suspend. So, this patch fixes
> the
The USB gadget subsystem wants to use the USB debugfs root directory, so
move it to the common "core" USB code so that it is properly initialized
and removed as needed.
In order to properly do this, we need to load the common code before the
usb core code, when everything is linked into the
>
> On Tue 04 Jun 22:50 PDT 2019, Avri Altman wrote:
>
> > Hi,
> >
> > >
> > > On Tue, Jun 4, 2019 at 12:22 AM Bjorn Andersson
> > > wrote:
> > > >
> > > > This series exposes the ufs_reset line as a gpio, adds support for
> > > > ufshcd to
> > > > acquire and toggle this and then adds this to
On Tue, 04 Jun 2019, Mauro Carvalho Chehab wrote:
> WARNING: kernel-doc './scripts/kernel-doc -rst -enable-lineno -function
> Hardware workarounds ./drivers/gpu/drm/i915/intel_workarounds.c' failed with
> return code 1
> WARNING: kernel-doc './scripts/kernel-doc -rst -enable-lineno -function
>
On Fri 31-05-19 14:53:35, David Rientjes wrote:
> On Fri, 31 May 2019, Michal Hocko wrote:
>
> > > The problem which this patch addresses has apparently gone unreported for
> > > 4+ years since
> >
> > Can we finaly stop considering the time and focus on the what is the
> > most reasonable
On 04.06.19 18:52, Andy Shevchenko wrote:
On Mon, Jun 03, 2019 at 10:33:32AM +0200, Stefan Roese wrote:
From: Yegor Yefremov
This patch permits the usage for GPIOs to control
the CTS/RTS/DTR/DSR/DCD/RI signals.
+ if (up->gpios) {
+ mctrl_gpio_set(up->gpios,
I suspect that if I compile the following using gcc-9 It'll bleat
about going beyond the end of the array:
#define _GNU_SOURCE
#include
#define MAX_CPU 2048
int fubar(void)
{
cpu_set_t *set = CPU_ALLOC(MAX_CPU);
CPU_SET_S(MAX_CPU - 2, CPU_ALLOC_SIZE(MAX_CPU), set);
Hi Nicolas,
Am 04.06.19 um 19:32 schrieb Nicolas Saenz Julienne:
> Hi all,
> this series aims at adding cpufreq support to the Raspberry Pi family of
> boards.
>
> The previous revision can be found at: https://lkml.org/lkml/2019/5/20/431
>
> The series first factors out 'pllb' from clk-bcm2385
On 2019年06月03日 18:53, Jim Lin wrote:
The Clear_TT_Buffer request sent to the hub includes the address of
the LS/FS child device in wValue field. usb_hub_clear_tt_buffer()
uses udev->devnum to set the address wValue. This won't work for
devices connected to xHC.
For other host controllers
On Wed, Jun 05, 2019 at 02:02:40AM +, Duyanlin wrote:
>
> If the function usb_maxpacket(urb->dev, urb->pipe, usb_pipeout(urb->pipe))
> returns 0, that will cause a illegal divide-by-zero operation, unexpected
> results may occur.
> It is best to ensure that the denominator is non-zero
On Tue, Jun 04, 2019 at 06:29:47PM +0200, Clément Péron wrote:
> Allwinner A31 has introduced a new memory mapping and a
> reset line.
>
> The difference in memory mapping are :
>
> - In the configure register there is a new sample bit
> and Allwinner has introduced the active threshold feature.
On Tue, Jun 04, 2019 at 06:29:48PM +0200, Clément Péron wrote:
> This driver is used in various Allwinner SoC with different configuration.
>
> Introduce a quirks struct to know the fifo size and if a reset is required.
>
> Signed-off-by: Clément Péron
> Acked-by: Sean Young
Acked-by: Maxime
On Tue, Jun 04, 2019 at 06:29:49PM +0200, Clément Péron wrote:
> Allwiner A31 has a different memory mapping so add the compatible
> we will need it later.
>
> Signed-off-by: Clément Péron
> Acked-by: Sean Young
Acked-by: Maxime Ripard
Maxime
--
Maxime Ripard, Bootlin
Embedded Linux and
On Tue, Jun 04, 2019 at 06:29:50PM +0200, Clément Péron wrote:
> We are using RXINT bits definition when looking at RXSTA register.
>
> These bits are equal but it's not really proper.
>
> Introduce the RXSTA bits and use them to have coherency.
>
> Signed-off-by: Clément Péron
> ---
>
OK for me.
Erwan.
On 6/5/19 9:08 AM, Fabrice Gasnier wrote:
> Un autre qu'on avait pas vu...
>
>
> Forwarded Message
> Subject: [PATCH -next] serial: stm32: Make stm32_get_databits static
> Date: Tue, 28 May 2019 17:04:49 +0800
> From: YueHaibing
> To:
On Wed, 05 Jun 2019, Lee Jones wrote:
> On Tue, 04 Jun 2019, Bjorn Andersson wrote:
>
> > On Tue 04 Jun 03:44 PDT 2019, Lee Jones wrote:
> > > diff --git a/drivers/usb/dwc3/dwc3-qcom.c b/drivers/usb/dwc3/dwc3-qcom.c
> > [..]
> > > @@ -373,7 +416,7 @@ static int dwc3_qcom_clk_init(struct
selftests bpf test_sock_fields
selftests: bpf_test_sock_fields [FAIL]
Full test log,
https://qa-reports.linaro.org/lkft/linux-next-oe/build/next-20190605/testrun/761646/log
Config:
http://snapshots.linaro.org/openembedded/lkft/lkft/sumo/intel-corei7-64/lkft/linux-next/536/config
Test results
From: Oleg Nesterov [mailto:o...@redhat.com]
> Sent: 05 June 2019 10:25
> On 06/05, David Laight wrote:
> >
> > epoll() would have:
> > if (restore_user_sigmask(xxx.sigmask, , !ret || ret == -EINTR))
> > ret = -EINTR;
>
> I don't think so but lets discuss this later.
I certainly
Am 05.06.19 um 11:11 schrieb Nicolas Saenz Julienne:
> On Tue, 2019-06-04 at 17:00 -0700, Eric Anholt wrote:
>> Nicolas Saenz Julienne writes:
>>
>>> Registers clk-raspberrypi as a platform device as part of the driver's
>>> probe sequence.
>> Similar to how we have VCHI register platform devices
On Tue, Jun 04, 2019 at 12:43:40PM -0500, Dan Murphy wrote:
> The use of and enablement of the GPIO can be used across devices.
> Use the enable_reg in the regulator descriptor for the register to
> write.
>
> Signed-off-by: Dan Murphy
> Signed-off-by: Jacek Anaszewski
> ---
>
> v5 - No
On 06/04, Song Liu wrote:
>
> Currently, uprobe swaps the target page with a anonymous page in both
> install_breakpoint() and remove_breakpoint(). When all uprobes on a page
> are removed, the given mm is still using an anonymous page (not the
> original page).
Agreed, it would be nice to avoid
On Tue, Jun 04, 2019 at 05:20:15PM +0200, Enric Balletbo i Serra wrote:
> There is a bit of mess between cros-ec mfd includes and platform
> includes. For example, we have a linux/mfd/cros_ec.h include that
> exports the interface implemented in platform/chrome/cros_ec_proto.c. Or
Acked-by: Mark
On Wed, Jun 05, 2019 at 11:05:56AM +0200, Eugeniu Rosca wrote:
> From: Spyridon Papageorgiou
>
> When a USB device fails to enumerate, only a kernel message is printed.
> With this patch, a uevent is also generated to notify userspace.
> Services can monitor for the event through udev and handle
Patch adds usb_decode_test_mode and usb_decode_device_feature functions,
which allow to make more readable and simplify the
usb_decode_set_clear_feature function.
Signed-off-by: Pawel Laszczak
---
drivers/usb/common/debug.c | 89 ++
1 file changed, 43
As a zpool_driver, zsmalloc can allocate movable memory because it
support migate pages.
But zbud and z3fold cannot allocate movable memory.
This commit adds malloc_support_movable to zpool_driver.
If a zpool_driver support allocate movable memory, set it to true.
And add
This is the third version that was updated according to the comments
from Sergey Senozhatsky https://lkml.org/lkml/2019/5/29/73 and
Shakeel Butt https://lkml.org/lkml/2019/6/4/973
zswap compresses swap pages into a dynamically allocated RAM-based
memory pool. The memory pool should be zbud,
From: Wanpeng Li
Make lapic timer unpinned when timer is injected by posted-interrupt,
the emulated timer can be offload to the housekeeping cpus.
This patch introduces a new kvm module parameter, it is false by default.
The host admin can enable it after fine tuned, e.g. dedicated instances
On Wed, Jun 5, 2019 at 3:03 PM Greg KH wrote:
>
> On Tue, Jun 04, 2019 at 10:22:05PM -0700, Joe Perches wrote:
> > On Wed, 2019-06-05 at 07:10 +0200, Greg KH wrote:
> > > On Wed, Jun 05, 2019 at 01:10:41PM +0900, Masahiro Yamada wrote:
> > > > On Wed, Jun 5, 2019 at 3:21 AM Arnd Bergmann wrote:
Dedicated instances are currently disturbed by unnecessary jitter due
to the emulated lapic timers fire on the same pCPUs which vCPUs resident.
There is no hardware virtual timer on Intel for guest like ARM. Both
programming timer in guest and the emulated timer fires incur vmexits.
This
From: Wanpeng Li
Dedicated instances are currently disturbed by unnecessary jitter due
to the emulated lapic timers fire on the same pCPUs which vCPUs resident.
There is no hardware virtual timer on Intel for guest like ARM. Both
programming timer in guest and the emulated timer fires incur
Hi,
> > Really need to split for different planes? I'd like a
> > VFIO_IRQ_SUBTYPE_GFX_DISPLAY_EVENT
> > so user space can probe change for all.
> User space can choose to user different handlers according to the
> specific event. For example, user space might not want to handle every
> cursor
From: Wanpeng Li
When lapic timer is injected by posted-interrupt, the emulated timer is
offload to the housekeeping cpu. The timer interrupt will be delivered
properly, no need to migrate timer.
Cc: Paolo Bonzini
Cc: Radim Krčmář
Signed-off-by: Wanpeng Li
---
arch/x86/kvm/lapic.c | 3 ++-
This patch aim at documenting USB related dt-bindings for the
Cadence USBSS-DRD controller.
Signed-off-by: Pawel Laszczak
Reviewed-by: Rob Herring
---
.../devicetree/bindings/usb/cdns-usb3.txt | 30 +++
1 file changed, 30 insertions(+)
create mode 100644
Em Tue, 04 Jun 2019 22:22:05 -0700
Joe Perches escreveu:
> On Wed, 2019-06-05 at 07:10 +0200, Greg KH wrote:
> > On Wed, Jun 05, 2019 at 01:10:41PM +0900, Masahiro Yamada wrote:
> > > On Wed, Jun 5, 2019 at 3:21 AM Arnd Bergmann wrote:
> []
> > > This means we cannot reliably use
Controller for OUT endpoints has shared on-chip buffers for all incoming
packets, including ep0out. It's FIFO buffer, so packets must be handled
by DMA in correct order. If the first packet in the buffer will not be
handled, then the following packets directed for other endpoints and
functions
Patch moves switch responsible for decoding descriptor type
outside snprintf. It improves code readability a little.
Signed-off-by: Pawel Laszczak
---
drivers/usb/common/debug.c | 113 +++--
1 file changed, 58 insertions(+), 55 deletions(-)
diff --git
Hi,
I have encountered a kernel BUG when running ltp ftrace-stress-test
on 4.19.48.
[ 209.704855] LTP: starting ftrace-stress-test (ftrace_stress_test.sh 90)
[ 209.739412] Scheduler tracepoints stat_sleep, stat_iowait, stat_blocked and
stat_runtime require the kernel parameter
On Thu, May 23, 2019 at 01:25:08PM +0300, Amir Goldstein wrote:
...
> > > > Interesting. When do you think the gate can be removed?
> > >
> > > Nobody is working on this AFAIK.
> > > What I posted was a simple POC, but I have no use case for this.
> > > In the patchwork link above, Jan has
From: Claudiu Beznea
Add compatible string for SAM9X60 HLCDC's PWM.
Signed-off-by: Claudiu Beznea
Acked-by: Thierry Reding
---
Hi Thierry,
This patch was initially part of series at [1]. The rest of the patches in
that series were taken though drm-misc-next. Only this one remained.
[1]
Hi
> > > > > Sounds like a bug to me...should fix it first by marking the
> > > > > data registers as volatile.
> > > > >
> > > > The ETDR is a writable register, it is not volatile. Even we
> > > > change it to Volatile, I don't think we can't avoid this issue.
> > > > for the regcache_sync Just
On Wed, Jun 05, 2019 at 12:54:12AM +0530, Bhardwaj, Rajneesh wrote:
> Hi Andy
>
> On 04-Jun-19 9:39 PM, Andy Shevchenko wrote:
> > On Thu, May 30, 2019 at 06:08:27PM +0530, Rajneesh Bhardwaj wrote:
> > > Add the CPUID model number of Icelake Neural Network Processor for Deep
> > I believe we
This patch introduces new Cadence USBSS DRD driver to Linux kernel.
The Cadence USBSS DRD Driver is a highly configurable IP Core which
can be instantiated as Dual-Role Device (DRD), Peripheral Only and
Host Only (XHCI)configurations.
The current driver has been validated with FPGA burned. We
Hi Nicolas,
Am 04.06.19 um 19:32 schrieb Nicolas Saenz Julienne:
> Raspberry Pi's firmware offers and interface though which update it's
> clock's frequencies. This is specially useful in order to change the CPU
> clock (pllb_arm) which is 'owned' by the firmware and we're unable to
> scale using
Am 04.06.19 um 19:32 schrieb Nicolas Saenz Julienne:
> Raspberry Pi's firmware controls this pll, we should use the firmware
> interface to access it.
>
> Signed-off-by: Nicolas Saenz Julienne
> ---
> drivers/clk/bcm/clk-bcm2835.c | 25 -
> 1 file changed, 25 deletions(-)
This series introduces support for Amazon's Annapurna Labs Fabric Interrupt
Controller.
The Amazon's Annapurna Labs FIC (Fabric Interrupt Controller) has 32
inputs/sources. This FIC may be cascaded into another FIC or connected
directly to the main CPU Interrupt Controller (e.g. GIC).
Changes
Document Amazon's Annapurna Labs Fabric Interrupt Controller SoC binding.
Signed-off-by: Talel Shenhar
---
.../interrupt-controller/amazon,al-fic.txt | 22 ++
1 file changed, 22 insertions(+)
create mode 100644
The Amazon's Annapurna Labs Fabric Interrupt Controller has 32 inputs
lines. A FIC (Fabric Interrupt Controller) may be cascaded into another FIC
or directly to the main CPU Interrupt Controller (e.g. GIC).
Signed-off-by: Talel Shenhar
---
MAINTAINERS | 6 +
On Wed, 5 Jun 2019 at 00:53, Paolo Bonzini wrote:
>
> On 21/05/19 08:06, Wanpeng Li wrote:
> > From: Wanpeng Li
> >
> > Allow guest reads CORE cstate when exposing host CPU power management
> > capabilities
> > to the guest. PKG cstate is restricted to avoid a guest to get the whole
> >
On 05.06.19 10:58, David Hildenbrand wrote:
>>> /*
>>> * For now, we have a linear search to go find the appropriate
>>> * memory_block corresponding to a particular phys_index. If
>>> @@ -658,6 +670,11 @@ static int init_memory_block(struct memory_block
>>> **memory, int block_id,
>>>
1 - 100 of 928 matches
Mail list logo
