On Mon, Aug 12, 2019 at 08:20:43AM -0700, Alexander Duyck wrote:
> On Mon, Aug 12, 2019 at 2:53 AM Michael S. Tsirkin wrote:
> >
> > On Wed, Aug 07, 2019 at 03:42:19PM -0700, Alexander Duyck wrote:
> > > From: Alexander Duyck
>
>
>
> > > --- a/include/uapi/linux/virtio_balloon.h
> > > +++ b/in
On 10/23/18 9:19 PM, Suman Anna wrote:
> The virtio_rpmsg_bus driver uses the "%p" format-specifier for
> printing the vring buffer address. This prints only a hashed
> pointer even for previliged users. Use "%pK" instead so that
> the address can be printed during debug using kptr_restrict
> sysct
On 12.08.19 17:20, Alexander Duyck wrote:
> On Mon, Aug 12, 2019 at 2:53 AM Michael S. Tsirkin wrote:
>>
>> On Wed, Aug 07, 2019 at 03:42:19PM -0700, Alexander Duyck wrote:
>>> From: Alexander Duyck
>
>
>
>>> --- a/include/uapi/linux/virtio_balloon.h
>>> +++ b/include/uapi/linux/virtio_balloon
From: Joe Burmeister
> Sent: 09 August 2019 13:54
>
> Many, though not all, AT25s have an instruction for chip erase.
> If there is one in the datasheet, it can be added to device tree.
> Erase can then be done in userspace via the sysfs API with a new
> "erase" device attribute. This matches the
On 2019-08-11 10:01 p.m., Greentime Hu wrote:
> Hi Logan,
>
> Logan Gunthorpe 於 2019年8月10日 週六 上午3:03寫道：
>>
>>
>>
>> On 2019-08-09 11:01 a.m., Greentime Hu wrote:
>>> Hi Logan,
>>>
>>> Logan Gunthorpe 於 2019年8月9日 週五 下午11:47寫道：
On 2019-08-08 10:23 p.m., Greentime Hu wrote:
>
On Wed, Jul 31, 2019 at 02:58:27PM +0900, Masahiro Yamada wrote:
> Hi Joe,
>
>
> On Thu, May 9, 2019 at 11:39 PM Joe Lawrence wrote:
> >
> > From: Miroslav Benes
> >
> > Currently, livepatch infrastructure in the kernel relies on
> > MODULE_INFO(livepatch, "Y") statement in a livepatch module.
> -Original Message-
> From: Lorenzo Pieralisi
> Sent: Monday, August 12, 2019 11:39 AM
> To: Haiyang Zhang
> Cc: sas...@kernel.org; bhelg...@google.com; linux-
> hyp...@vger.kernel.org; linux-...@vger.kernel.org; KY Srinivasan
> ; Stephen Hemminger ;
> o...@aepfle.de; vkuznets ; linux
On Fri, Aug 9, 2019 at 2:47 PM Daniel Xu wrote:
>
> It's useful to know [uk]probe's nmissed and nhit stats. For example with
> tracing tools, it's important to know when events may have been lost.
> debugfs currently exposes a control file to get this information, but
> it is not compatible with p
On Fri, Aug 9, 2019 at 2:48 PM Daniel Xu wrote:
>
> It is sometimes necessary to perform ioctl's on the underlying perf fd.
> There is not currently a way to extract the fd given a bpf_link, so add a
> a pair of casting and getting helpers.
>
> The casting and getting helpers are nice because they
When calling request_threaded_irq() with a CP2112, the function
cp2112_gpio_irq_startup() is called in a IRQ context.
Therefore we can not sleep, and we can not call
cp2112_gpio_direction_input() there.
Move the call to cp2112_gpio_direction_input() earlier to have a working
driver.
Signed-off-b
Following the discussions on v2 of this patch(set) [1], this series
takes slightly different approach:
- it implements its own simple memory pool that does not rely on the
slab allocator
- drops the early log buffer logic entirely since it can now allocate
metadata from the memory pool direct
Object scan areas are an optimisation aimed to decrease the false
positives and slightly improve the scanning time of large objects known
to only have a few specific pointers. If a struct scan_area fails to
allocate, kmemleak can still function normally by scanning the full
object.
Introduce an OB
Currently kmemleak uses a static early_log buffer to trace all memory
allocation/freeing before the slab allocator is initialised. Such early
log is replayed during kmemleak_init() to properly initialise the
kmemleak metadata for objects allocated up that point. With a memory
pool that does not rel
Add a memory pool for struct kmemleak_object in case the normal
kmem_cache_alloc() fails under the gfp constraints passed by the caller.
The mem_pool[] array size is currently fixed at 16000.
Signed-off-by: Catalin Marinas
---
mm/kmemleak.c | 54 +-
Both the G700 and the G700s are sharing the same receiver.
Include support for this receiver in hid-logitech-dj so that userspace
can differentiate both.
Signed-off-by: Benjamin Tissoires
---
drivers/hid/hid-logitech-dj.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/hid/hid-l
On Mon, 2019-08-12 at 11:33 -0400, Sasha Levin wrote:
> On Mon, Aug 12, 2019 at 03:22:26PM +0200, Michal Hocko wrote:
> > On Mon 12-08-19 15:14:12, Vlastimil Babka wrote:
> > > On 8/12/19 10:45 AM, Michal Hocko wrote:
> > > > On Sun 11-08-19 19:46:14, Sasha Levin wrote:
> > > > > On Fri, Aug 09, 20
> arch/ia64/sn/pci/tioce_provider.c | 4 ++--
Thanks for the patch, but Christoph is working on a patch series that deletes
all of arch/ia64/sn/
-Tony
On Mon, Aug 12, 2019 at 8:50 AM David Hildenbrand wrote:
>
> On 12.08.19 17:20, Alexander Duyck wrote:
> > On Mon, Aug 12, 2019 at 2:53 AM Michael S. Tsirkin wrote:
> >>
> >> On Wed, Aug 07, 2019 at 03:42:19PM -0700, Alexander Duyck wrote:
> >>> From: Alexander Duyck
> >
> >
> >
> >>> --- a/inc
On Mon, Aug 12, 2019 at 7:11 AM Arnd Bergmann wrote:
>
> On Mon, Aug 12, 2019 at 3:25 PM Ben Hutchings
> wrote:
> > On Sat, 2019-08-10 at 13:44 -0700, Deepa Dinamani wrote:
> > > On Mon, Aug 5, 2019 at 7:14 AM Ben Hutchings
> > > wrote:
> > > > On Mon, 2019-07-29 at 18:49 -0700, Deepa Dinamani w
On Mon, Aug 12, 2019 at 11:38:53AM +0100, Lee Jones wrote:
> On Tue, 06 Aug 2019, Charles Keepax wrote:
>
> > Add the ability to get the clock for each clock input pin of the chip
> > and enable MCLK2 since that is expected to be a permanently enabled
> > 32kHz clock.
> >
> > Signed-off-by: Charl
On Mon, Aug 12, 2019 at 9:09 AM Deepa Dinamani wrote:
>
> On Mon, Aug 12, 2019 at 7:11 AM Arnd Bergmann wrote:
> >
> > On Mon, Aug 12, 2019 at 3:25 PM Ben Hutchings
> > wrote:
> > > On Sat, 2019-08-10 at 13:44 -0700, Deepa Dinamani wrote:
> > > > On Mon, Aug 5, 2019 at 7:14 AM Ben Hutchings
> >
On Mon, Aug 12, 2019 at 04:12:36PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the rcu tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
>
> arch/x86/xen/smp_pv.c: In function 'xen_pv_play_dead':
> arch/x86/xen/smp_pv.c:439:2: error: implicit declaration of f
This can help debugging the situation
Signed-off-by: Benjamin Tissoires
---
Hi,
not entirely sure if we can use this in a such simple way.
However, this is useful to mimic device behaviour from userspace.
Cheers,
Benjamin
drivers/hid/uhid.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion
This panel is not very friendly to us:
it exposes multiple multitouch collections, some of them being of
logical application stylus.
Usually, a device has only one report per application, and that is
what I assumed in commit 8dfe14b3b47f ("HID: multitouch: ditch mt_report_id")
To avoid breaking a
It was a good idea at the time to not create a mouse node for the
multitouch touchscreens, but:
- touchscreens following the Win 8 protocol should not have this
disturbing mouse node anymore, or if they have, it should be
used for something else (like a joystick attached to the screen)
- touchp
First one should prevent us to add more quirks for Win8 devices
that have a trackstick.
Second one is a weird device that doesnt work properly in recent
kernels.
Cheers,
Benjamin
Benjamin Tissoires (2):
HID: multitouch: do not filter mice nodes
HID: multitouch: add support for the Smart Tech
On Mon, Aug 12, 2019 at 8:29 AM Steven Rostedt wrote:
> From what I understand, Matthew's "lockdown" work is to prevent the
> system from doing anything to see what is happening in the kernel. This
> includes tracefs. This looks like it is working as designed.
Oopsing the kernel isn't working as
11.08.2019 22:15, Sowjanya Komatineni пишет:
>
> On 8/11/19 10:39 AM, Dmitry Osipenko wrote:
>> 09.08.2019 21:40, Sowjanya Komatineni пишет:
>>> On 8/9/19 11:18 AM, Dmitry Osipenko wrote:
09.08.2019 19:19, Sowjanya Komatineni пишет:
> On 8/9/19 6:56 AM, Dmitry Osipenko wrote:
>> 09.08
Hi,
On 12-08-19 18:08, Benjamin Tissoires wrote:
Both the G700 and the G700s are sharing the same receiver.
Include support for this receiver in hid-logitech-dj so that userspace
can differentiate both.
Signed-off-by: Benjamin Tissoires
Nice, looks good to me:
Reviewed-by: Hans de Goede
R
This is a common pattern in the HID drivers to reset the drvdata.
However, this is actually already handled by driver core, so there
is no need to do it manually.
Signed-off-by: Benjamin Tissoires
---
drivers/hid/wacom_sys.c | 18 +-
1 file changed, 5 insertions(+), 13 deletions(
Hi,
the wacom one is split dfrom the other drivers as the change is slightly
bigger.
Cheers,
Benjamin
Benjamin Tissoires (2):
HID: do not call hid_set_drvdata(hdev, NULL) in drivers
HID: wacom: do not call hid_set_drvdata(hdev, NULL)
drivers/hid/hid-cougar.c | 6 ++
drivers/hid/
This is a common pattern in the HID drivers to reset the drvdata. Some
do it properly, some do it only in case of failure.
But, this is actually already handled by driver core, so there is no need
to do it manually.
Signed-off-by: Benjamin Tissoires
---
drivers/hid/hid-cougar.c | 6 ++
On Sat, Aug 10, 2019 at 8:06 PM Joe Perches wrote:
>
> On Sat, 2019-08-10 at 19:04 -0700, Nathan Chancellor wrote:
> > On a tangential note, how are you planning on doing the fallthrough
> > comment to attribute conversion? The reason I ask is clang does not
> > support the comment annotations, me
On 12/08/19 17:09, Charles Keepax wrote:
On Mon, Aug 12, 2019 at 11:38:53AM +0100, Lee Jones wrote:
On Tue, 06 Aug 2019, Charles Keepax wrote:
Add the ability to get the clock for each clock input pin of the chip
and enable MCLK2 since that is expected to be a permanently enabled
32kHz clock.
On 8/12/19 10:47 AM, Andrew F. Davis wrote:
> On 10/23/18 9:19 PM, Suman Anna wrote:
>> The virtio_rpmsg_bus driver uses the "%p" format-specifier for
>> printing the vring buffer address. This prints only a hashed
>> pointer even for previliged users. Use "%pK" instead so that
>> the address can b
On Mon, Aug 12, 2019 at 6:03 AM Stephen Douthit
wrote:
>
> On 8/10/19 3:43 AM, Christoph Hellwig wrote:
> > On Thu, Aug 08, 2019 at 08:24:31PM +, Stephen Douthit wrote:
> >> Intel moved the PCS register from 0x92 to 0x94 on Denverton for some
> >> reason, so now we get to check the device ID b
Hi Arnd,
> All these ioctl commands are compatible, so we can handle
> them with a trivial wrapper in rfcomm/sock.c and remove
> the listing in fs/compat_ioctl.c.
>
> Signed-off-by: Arnd Bergmann
> ---
> fs/compat_ioctl.c | 6 --
> net/bluetooth/rfcomm/sock.c | 14 --
>
Hi Arnd,
> All these ioctl commands are compatible, so we can handle
> them with a trivial wrapper in hci_sock.c and remove
> the listing in fs/compat_ioctl.c.
>
> A few of the commands pass integer arguments instead of
> pointers, so for correctness skip the compat_ptr() conversion
> here.
>
>
Hi!
On 08/08/2019 04:38, Gustavo A. R. Silva wrote:
Mark switch cases where we are expecting to fall through.
Fix the following warnings (Building: arm-ep93xx_defconfig arm):
arch/arm/mach-ep93xx/crunch.c: In function 'crunch_do':
arch/arm/mach-ep93xx/crunch.c:46:3: warning: this statement may
Hi Alex,
> From the perspective of controller, global suspend means there is no
> SET_FEATURE (DEVICE_REMOTE_WAKEUP) and controller would drop the
> firmware. It would consume less power. So we should not send this kind
> of SET_FEATURE when host goes to suspend state.
> Otherwise, when making dev
Hi Alex,
> usb reset resume will cause downloading firmware again and
> requesting firmware may be failed while host is resuming
>
> Signed-off-by: Alex Lu
> ---
> drivers/bluetooth/btrtl.c | 101 --
> 1 file changed, 97 insertions(+), 4 deletions(-)
>
> diff
On 8/12/19 12:28 PM, Suman Anna wrote:
> On 8/12/19 10:47 AM, Andrew F. Davis wrote:
>> On 10/23/18 9:19 PM, Suman Anna wrote:
>>> The virtio_rpmsg_bus driver uses the "%p" format-specifier for
>>> printing the vring buffer address. This prints only a hashed
>>> pointer even for previliged users. U
Hi Claire,
> commit 32646db8cc28 ("Bluetooth: btqca: inject command complete event
> during fw download") added qca_inject_cmd_complete_event() for certain
> qualcomm chips. However, qca_download_firmware() will return without
> calling release_firmware() in this case.
>
> This leads to a memory
On 08/11, Adrian Reber wrote:
>
> include/linux/pid.h| 2 +-
> include/linux/sched/task.h | 1 +
> include/uapi/linux/sched.h | 1 +
> kernel/fork.c | 22 --
> kernel/pid.c | 36 +---
> 5 files changed, 52 in
On Mon, 2019-08-12 at 18:27 +0200, Benjamin Tissoires wrote:
> This is a common pattern in the HID drivers to reset the drvdata.
> Some
> do it properly, some do it only in case of failure.
>
> But, this is actually already handled by driver core, so there is no
> need
> to do it manually.
>
> Si
On 8/12/19 11:36 AM, Andrew F. Davis wrote:
> On 8/12/19 12:28 PM, Suman Anna wrote:
>> On 8/12/19 10:47 AM, Andrew F. Davis wrote:
>>> On 10/23/18 9:19 PM, Suman Anna wrote:
The virtio_rpmsg_bus driver uses the "%p" format-specifier for
printing the vring buffer address. This prints only
On Mon, Aug 12, 2019 at 1:21 PM Hans de Goede wrote:
>
> There are 2 problems with the old iosf PMIC I2C bus arbritration code which
> this commit fixes:
>
> 1. The lockdep code complains about a possible deadlock in the
> iosf_mbi_[un]block_punit_i2c_access code:
>
> [6.712662] ==
23.06.2019 20:07, Dmitry Osipenko пишет:
> Enable IOMMU support for the video decoder.
>
> Signed-off-by: Dmitry Osipenko
> ---
>
> No changes since v1.
>
> arch/arm/boot/dts/tegra30.dtsi | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm/boot/dts/tegra30.dtsi b/arch/arm/boot/d
23.07.2019 6:37, Dmitry Osipenko пишет:
> Add timings for RAM codes 4 and 6 and a timing for 528mHz of RAM code 1,
> which was missed due to the clock driver bug that is fixed now in all of
> stable kernels.
>
> Tested-by: Steev Klimaszewski
> Signed-off-by: Dmitry Osipenko
Friendly ping :)
Up until now, the pata_buddha driver would only check for cards on
initcall time. Now, the kernel will call its probe function as soon
as a compatible card is detected.
v5: Remove module_exit(): There's no good way to handle the X-Surf hack.
Also include a workaround to save X-Surf's drvdata i
On 8/12/19 12:39 PM, Suman Anna wrote:
> On 8/12/19 11:36 AM, Andrew F. Davis wrote:
>> On 8/12/19 12:28 PM, Suman Anna wrote:
>>> On 8/12/19 10:47 AM, Andrew F. Davis wrote:
On 10/23/18 9:19 PM, Suman Anna wrote:
> The virtio_rpmsg_bus driver uses the "%p" format-specifier for
> print
On 08/12/2019 06:48 PM, Max Staudt wrote:
> +/*
> + * We cannot have a modalias for X-Surf boards, as it competes with the
> + * zorro8390 network driver. As a stopgap measure until we have proper
> + * MFC support for this board, we manually attach to it late after Zorro
> + * has enumerated its b
Hi Dmitry,
On Fri, Aug 9, 2019 at 7:35 PM Dmitry Torokhov
wrote:
>
> Separating "normal" and "polled" input devices was a mistake, as often we
> want to allow the very same device work on both interrupt-driven and
> polled mode, depending on the board on which the device is used.
>
> This introdu
On Mon, Aug 12, 2019 at 12:45 PM Luis de Oliveira
wrote:
> From: Andy Shevchenko
> Date: Sat, Aug 10, 2019 at 14:09:21
> > On Fri, Aug 9, 2019 at 5:38 PM Sakari Ailus wrote:
> > > On Tue, Jun 11, 2019 at 09:20:51PM +0200, Luis Oliveira wrote:
> > > > + of_id = of_match_node(dw_mipi_csi_of_m
On Mon, Aug 12, 2019 at 06:37:10PM +0200, Oleg Nesterov wrote:
> On 08/11, Adrian Reber wrote:
> >
> > include/linux/pid.h| 2 +-
> > include/linux/sched/task.h | 1 +
> > include/uapi/linux/sched.h | 1 +
> > kernel/fork.c | 22 --
> > kernel/pid.c
On Mon, Aug 12, 2019 at 07:37:51AM +0200, Christophe Leroy wrote:
>
>
> Le 12/08/2019 à 04:32, Nathan Chancellor a écrit :
> > Commit aea447141c7e ("powerpc: Disable -Wbuiltin-requires-header when
> > setjmp is used") disabled -Wbuiltin-requires-header because of a warning
> > about the setjmp an
Hi João,
On Thu, Aug 8, 2019 at 10:35 PM João Moreno wrote:
>
> Hi Benjamin,
>
> On Mon, 8 Jul 2019 at 22:35, João Moreno wrote:
> >
> > Hi Benjamin,
> >
> > No worries, also pretty busy over here. Didn't mean to press.
> >
> > On Mon, 1 Jul 2019 at 10:32, Benjamin Tissoires
> > wrote:
> > >
>
On 08/12, Christian Brauner wrote:
> On Mon, Aug 12, 2019 at 06:37:10PM +0200, Oleg Nesterov wrote:
> > On 08/11, Adrian Reber wrote:
> > >
> > > include/linux/pid.h| 2 +-
> > > include/linux/sched/task.h | 1 +
> > > include/uapi/linux/sched.h | 1 +
> > > kernel/fork.c |
Document the compatible for ANV32E61W 64kb Serial SPI non-volatile SRAM.
Although it is a SRAM device, it can be accessed through EEPROM
interface. At least until there is no proper SRAM driver support for
it.
Signed-off-by: Krzysztof Kozlowski
Reviewed-by: Fabio Estevam
---
Changes since v4:
Add support for i.MX6UL modules from Kontron Electronics GmbH (before
acquisition: Exceet Electronics) and evalkit boards based on it:
1. N6310 SOM: i.MX6 UL System-on-Module, a 25x25 mm solderable module
(LGA pads and pin castellations) with 256 MB RAM, 1 MB NOR-Flash,
256 MB NAND and other
Add vendor prefix for Anvo-Systems Dresden GmbH.
Signed-off-by: Krzysztof Kozlowski
Reviewed-by: Rob Herring
---
Changes since v4:
None
Changes since v3:
1. Add Rob's tag,
2. Remove Admatec (not needed anymore).
Changes since v2:
1. Use admatecde vendor prefix.
2. Add Anvo-Systems Dresden Gm
On 8/12/19 2:34 AM, Michal Hocko wrote:
On Fri 09-08-19 16:54:43, Yang Shi wrote:
On 8/9/19 11:26 AM, Yang Shi wrote:
On 8/9/19 11:02 AM, Michal Hocko wrote:
[...]
I have to study the code some more but is there any reason why those
pages are not accounted as proper THPs anymore? Sure th
"PCI: dwc: al: Add support for DW based driver type"
Make $SUBJECT compliant with other host controllers patches.
On Tue, Jul 23, 2019 at 12:27:09PM +0300, Jonathan Chocron wrote:
> This driver is DT based and utilizes the DesignWare APIs.
> It allows using a smaller ECAM range for a larger bus r
Hi,
this time a more detailed look. :)
> Subject: Re: [PATCH v8 01/28] linkage: new macros for assembler symbols
Patch subject needs a verb, like, for example:
"linkage: Introduce new macros for assembler symbols"
On Thu, Aug 08, 2019 at 12:38:27PM +0200, Jiri Slaby wrote:
> Introduce new C ma
On Mon, Aug 12, 2019 at 06:57:34PM +0200, Oleg Nesterov wrote:
> On 08/12, Christian Brauner wrote:
> > On Mon, Aug 12, 2019 at 06:37:10PM +0200, Oleg Nesterov wrote:
> > > On 08/11, Adrian Reber wrote:
> > > >
> > > > include/linux/pid.h| 2 +-
> > > > include/linux/sched/task.h | 1 +
>
Hi Matthias,
> The qca_data structure is allocated with kzalloc() and hence
> zero-initialized. Remove a bunch of unnecessary explicit
> initializations of struct members to zero.
>
> Signed-off-by: Matthias Kaehlcke
> Reviewed-by: Balakrishna Godavarthi
> ---
> just noticed that this patch fel
On Fri, Aug 9, 2019 at 11:08 PM James Morris wrote:
> Please verify and test, as I had to make a few minor fixups for my v5.2
> base.
Thanks James - there's a few small fixups required, would you like
those as separate patches or should I just send you a fixed copy of
the original patchset?
Hi Yue,
> If CONFIG_ACPI is not set, gcc warn this:
>
> drivers/bluetooth/hci_bcm.c:831:39: warning:
> acpi_bcm_int_last_gpios defined but not used [-Wunused-const-variable=]
> drivers/bluetooth/hci_bcm.c:838:39: warning:
> acpi_bcm_int_first_gpios defined but not used [-Wunused-const-variable=]
On Mon, 12 Aug 2019, Aubrey Li wrote:
> On Mon, Aug 12, 2019 at 8:25 PM Thomas Gleixner wrote:
> >
> > On Mon, 12 Aug 2019, Li, Aubrey wrote:
> > > On 2019/8/9 20:54, Thomas Gleixner wrote:
> > > > + local_irq_disable();
> > > > /*
> > > > * Setup the APIC counter to maximum. There is
Hi Benjamin,
On Mon, Aug 12, 2019 at 06:50:38PM +0200, Benjamin Tissoires wrote:
> Hi Dmitry,
>
> On Fri, Aug 9, 2019 at 7:35 PM Dmitry Torokhov
> wrote:
> >
> > Separating "normal" and "polled" input devices was a mistake, as often we
> > want to allow the very same device work on both interrup
On Mon, 2019-08-12 at 10:36 -0500, Troy Benjegerdes wrote:
> > On Aug 9, 2019, at 8:43 PM, Atish Patra
> > wrote:
> >
> > In RISC-V, tlb flush happens via SBI which is expensive.
> > If the target cpumask contains a local hartid, some cost
> > can be saved by issuing a local tlb flush as we do th
On Mon, Aug 12, 2019 at 10:35:53AM +0300, Jussi Kivilinna wrote:
> Hello,
>
> On 12.8.2019 6.31, Nathan Chancellor wrote:
> > From: Vladimir Serbinenko
> >
> > clang doesn't recognise =l / =h assembly operand specifiers but apparently
> > handles C version well.
> >
> > lib/mpi/generic_mpih-mul
On Wed, Jun 19, 2019 at 12:34 AM Jiping Ma wrote:
Oops. Boris pointed out to me that this has been left hanging. Sorry
for the delay.
> 3rd Gen Core seems to work just like Skylake.
Maybe "just like all the other Xeon-E3 processors?
"3rd Gen Core" seems to be Ivybridge generation (based on the
Hi,
On 09-08-19 17:11, Yauhen Kharuzhy wrote:
On Fri, Aug 09, 2019 at 01:06:01PM +0200, Hans de Goede wrote:
Hi,
On 8/9/19 12:01 AM, Yauhen Kharuzhy wrote:
Intel Cherry Trail Whiskey Cove extcon driver connect USB data lines to
PMIC at driver probing for further charger detection. This causes
On Wed, Aug 07, 2019 at 01:50:42PM +0300, Dan Carpenter wrote:
> On Tue, Aug 06, 2019 at 06:41:44PM +0200, Oliver Hartkopp wrote:
> > I compiled the code (the original version), but I do not get that "Should it
> > be static?" warning:
> >
> > user@box:~/net-next$ make C=1
> > CALLscripts/ch
On Mon, Feb 26, 2018 at 12:40 PM Andi Kleen wrote:
>
> > Given the HSD143 errata and its possible relevance, have you tried
> > changing the magic number to 32, does it then still fix things?
> >
> > No real objection to the patch as such, it just needs a coherent comment
> > and a tested-by tag I
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
A: No.
Q: Should I include quotations after my reply?
http://daringfireball.net/2007/07/on_top
Woody,
On Mon, 12 Aug
On Wed, 2019-08-07 at 15:56 +0200, Thomas Gleixner wrote:
> Megha,
>
> On Tue, 6 Aug 2019, Megha Dey wrote:
> >
> > On Sat, 2019-06-29 at 09:59 +0200, Thomas Gleixner wrote:
> > >
> > > On Fri, 21 Jun 2019, Megha Dey wrote:
> > Totally agreed. The request to add a dynamic MSI-X infrastructure
>
Mein lieber Freund
Ich bin Frau Elizabeth Kerli James aus Deutschland. Ich lebe mein ganzes Leben
in
Die Vereinigten Staaten.
Ungefähr zwei Jahre lang wurde bei mir Krebs diagnostiziert und jetzt lüge ich
die
krankes Bett, ich möchte, dass du mir hilfst, meinen letzten Wunsch auf Erden
zu erfül
On Wed, 2019-08-07 at 15:18 +0100, Marc Zyngier wrote:
> On 07/08/2019 14:56, Thomas Gleixner wrote:
> >
> > Megha,
> >
> > On Tue, 6 Aug 2019, Megha Dey wrote:
> > >
> > > On Sat, 2019-06-29 at 09:59 +0200, Thomas Gleixner wrote:
> > > >
> > > > On Fri, 21 Jun 2019, Megha Dey wrote:
> > > Tota
On 8/12/19 9:25 AM, Dmitry Osipenko wrote:
11.08.2019 22:15, Sowjanya Komatineni пишет:
On 8/11/19 10:39 AM, Dmitry Osipenko wrote:
09.08.2019 21:40, Sowjanya Komatineni пишет:
On 8/9/19 11:18 AM, Dmitry Osipenko wrote:
09.08.2019 19:19, Sowjanya Komatineni пишет:
On 8/9/19 6:56 AM, Dmitry
On 8/7/19 8:37 PM, Rayagonda Kokatanur wrote:
From: Lori Hikichi
The driver does not support the SMBUS Quick command so remove the
flag that indicates that level of support.
By default the i2c_detect tool uses the quick command to try and
detect devices at some bus addresses. If the quick c
On Mon, Aug 12, 2019 at 10:00:40AM -0300, Jason Gunthorpe wrote:
> On Fri, Aug 09, 2019 at 03:58:30PM -0700, ira.we...@intel.com wrote:
> > From: Ira Weiny
> >
> > In order for MRs to be tracked against the open verbs context the ufile
> > needs to have a pointer to hand to the GUP code.
> >
> >
On 8/7/19 8:37 PM, Rayagonda Kokatanur wrote:
From: Lori Hikichi
Add the full name of the devicetree node to the adapter name.
Without this change, all adapters have the same name making it difficult
to distinguish between multiple instances.
The most obvious way to see this is to use the ut
Bjorn, this is v3 of the patchset. Christophs suggestion's required a
bit more rework than could be expressed in incremental patches so
I've resent the whole thing. I started with your p2pdma branch though
so it should have all the changes you already made. I've included a
range-diff from your p2pd
Push both PCI devices into the whitelist checking function seeing some
hardware will require us ensuring they are on the same host bridge.
At the same time we rename root_complex_whitelist() to
host_bridge_whitelist() to match the terminology used in the code.
Link: https://lore.kernel.org/r/2019
When a P2PDMA transfer is rejected due to ACS being set, we can also check
the whitelist and allow the transactions.
Do this by pushing the whitelist check into the upstream_bridge_distance()
function.
Link: https://lore.kernel.org/r/20190730163545.4915-6-log...@deltatee.com
Signed-off-by: Logan
The comment describing pci_p2pdma_distance_many() still referred to
the devices being behind the same root port. This no longer applies
so reword the documentation.
Link: https://lore.kernel.org/r/20190730163545.4915-15-log...@deltatee.com
Signed-off-by: Logan Gunthorpe
Signed-off-by: Bjorn Helga
Factor out the bus-only mapping into its own static function. No
functional changes. The original pci_p2pdma_map_sg_attrs() will be used to
decide whether this is an appropriate way to map.
Link: https://lore.kernel.org/r/20190730163545.4915-11-log...@deltatee.com
Signed-off-by: Logan Gunthorpe
Move the PCI bus offset from the generic dev_pagemap structure to a
specific pci_p2pdma_pagemap structure.
This structure will grow in subsequent patches.
Link: https://lore.kernel.org/r/20190730163545.4915-2-log...@deltatee.com
Signed-off-by: Logan Gunthorpe
Signed-off-by: Bjorn Helgaas
---
d
This is to match the dma_map_sg() API which this function will have to call
in an future patch.
Add a pci_p2pdma_map_sg_attrs() function and helper to call it with no
attributes just like the dma_map_sg() function.
Link: https://lore.kernel.org/r/20190730163545.4915-9-log...@deltatee.com
Signed-o
Add constant flags to indicate how two devices will be mapped or if they
are unsupported. upstream_bridge_distance() will now return the
mapping type and the distance in a passed-by-reference argument.
This helps annotate the code better, but the main reason is so we can use
the information to sto
The provider will be needed to figure out how to map a device.
Link: https://lore.kernel.org/r/20190730163545.4915-3-log...@deltatee.com
Signed-off-by: Logan Gunthorpe
Signed-off-by: Bjorn Helgaas
---
drivers/pci/p2pdma.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/pci/p2pdma.
When upstream_bridge_distance() is called, store the method required to map
the DMA transfers in an xarray so it can be looked up efficiently on the
hot path in pci_p2pdma_map_sg().
Link: https://lore.kernel.org/r/20190730163545.4915-12-log...@deltatee.com
Signed-off-by: Logan Gunthorpe
Signed-of
Intel devices do not have good support for P2P requests that span different
host bridges as the transactions will cross the QPI/UPI bus and this does
not perform well.
Therefore, enable support for these devices only if the host bridges match.
Add Intel devices that have been tested and are known
This is a prep patch to create a second level helper. There are no
functional changes.
The root complex whitelist code will be moved into this function in a
subsequent patch.
Link: https://lore.kernel.org/r/20190730163545.4915-5-log...@deltatee.com
Signed-off-by: Logan Gunthorpe
Signed-off-by: B
Any requests that traverse the host bridge will need to be mapped into the
IOMMU, so call dma_map_sg() inside pci_p2pdma_map_sg() when appropriate.
Similarly, call dma_unmap_sg() inside pci_p2pdma_unmap_sg().
Link: https://lore.kernel.org/r/20190730163545.4915-13-log...@deltatee.com
Signed-off-by
Now that we map the requests correctly we can remove the iommu_present()
restriction.
Link: https://lore.kernel.org/r/20190730163545.4915-14-log...@deltatee.com
Signed-off-by: Logan Gunthorpe
Signed-off-by: Bjorn Helgaas
---
drivers/pci/p2pdma.c | 4
1 file changed, 4 deletions(-)
diff --
Add pci_p2pdma_unmap_sg() to the two places that call pci_p2pdma_map_sg().
This is a prep patch to introduce correct mappings for p2pdma transactions
that go through the root complex.
Link: https://lore.kernel.org/r/20190730163545.4915-10-log...@deltatee.com
Signed-off-by: Logan Gunthorpe
Signed
Hi Wolfram,
On 8/6/19 9:09 PM, Rayagonda Kokatanur wrote:
From: Lori Hikichi
Enable handling of i2c repeated start. The current code
handles a multi msg i2c transfer as separate i2c bus
transactions. This change will now handle this case
using the i2c repeated start protocol. The number of msg
201 - 300 of 1141 matches
Mail list logo
