(Added CC: Thomas Meyer, Richard Weinberger)
On 2021-02-01, Petr Mladek wrote:
>> In preparation for removing printk's @logbuf_lock, dumpers that have
>> assumed to be protected against parallel calls must provide their own
>> synchronization. Add a locally static spinlock to synchronize the
>> k
It doesn't contain Jarkko's Tested-by and Reviewed-by tags though.
On 01/02/2021 17:48, Mickaël Salaün wrote:
> Hi,
>
> Yes, you can pull this patchset from here:
> https://github.com/l0kod/linux branch dyn-auth-blacklist-v5 (commit
> 33b94bcd56843b4235c6ba4a44157b3c5a8792f1).
>
> Mickaël
>
>
On 2/1/21 12:17 PM, Bhaskar Chowdhury wrote:
> s/debugees/debuge's/
Definitely not.
--
Bert Vermeulen
b...@biot.com
The Samsung Galaxy S5 uses the samsung s6e3fa2 AMOLED cmd LCD panel.
This driver was generated with [1], with the addition of
mipi_dsi_dcs_set_display_on at the end of the on method.
[1] https://github.com/msm8916-mainline/linux-mdss-dsi-panel-driver-generator
Signed-off-by: Iskren Chernev
---
The Samsung S6E3FA2 AMOLED cmd LCD panel is used on the Samsung Galaxy
S5 (klte).
Signed-off-by: Iskren Chernev
---
Add a simple generated panel driver that supports on/off and the corresponding
binding documentation.
Changes in v3:
- fix dt_binding_check issue with missing include
- fix panel t
John,
- Ursprüngliche Mail -
> Von: "John Ogness"
> An: "Petr Mladek"
> CC: "Sergey Senozhatsky" , "Sergey
> Senozhatsky" ,
> "Steven Rostedt" , "tglx" ,
> "linux-kernel" ,
> "Thomas Meyer" , "richard"
> Gesendet: Montag, 1. Februar 2021 17:51:14
> Betreff: Re: [PATCH printk-rework 09
On Sun, Jan 31, 2021 at 11:28 PM Nadav Amit wrote:
>
> > On Jan 31, 2021, at 12:32 PM, Andy Lutomirski wrote:
> >
> > On Sat, Jan 30, 2021 at 4:16 PM Nadav Amit wrote:
> >> From: Nadav Amit
> >>
> >> To detect deferred TLB flushes in fine granularity, we need to keep
> >> track on the completed
On 21-01-30 15:51:49, David Rientjes wrote:
> On Fri, 29 Jan 2021, Ben Widawsky wrote:
>
> > +static int cxl_mem_setup_mailbox(struct cxl_mem *cxlm)
> > +{
> > + const int cap = cxl_read_mbox_reg32(cxlm, CXLDEV_MB_CAPS_OFFSET);
> > +
> > + cxlm->mbox.payload_size =
> > + 1 << CXL_GET
On Mon, 1 Feb 2021 16:28:25 +
Max Gurtovoy wrote:
> In case allocation fails, we must behave correctly and exit with error.
>
> Signed-off-by: Max Gurtovoy
Fixes: e6b817d4b821 ("vfio-pci/zdev: Add zPCI capabilities to
VFIO_DEVICE_GET_INFO")
Reviewed-by: Cornelia Huck
I think this shoul
On Fri, 2021-01-29 at 09:23 +0100, Michal Hocko wrote:
> On Thu 28-01-21 13:05:02, James Bottomley wrote:
> > Obviously the API choice could be revisited
> > but do you have anything to add over the previous discussion, or is
> > this just to get your access control?
>
> Well, access control is ce
]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url:
https://github.com/0day-ci/linux/commits/Bilal-Wasim/Misc-bug-fixes-in-mtk-power-domain-drive
On Mon, Feb 01, 2021 at 12:49:24PM +, Christoph Hellwig wrote:
> DX_DEBUG is completely dead code, so either kill it off or make it an
> actual CONFIG_* symbol through Kconfig if it seems useful.
I wouldn't call it completely dead code. If you manually add "#define
DX_DEBUG" fs/ext4/namei.c c
sort -C is like sort -c >/dev/null but less portable. It fails on
busybox sort (i.e alpine linux).
Signed-off-by: Iskren Chernev
Fixes: ea5b8b5eb004 ("dt-bindings: Add a minimum version check for dtschema")
---
Documentation/devicetree/bindings/Makefile | 2 +-
1 file changed, 1 insertion(+), 1
On Mon, Feb 1, 2021 at 12:17 AM Aili Yao wrote:
>
> When one page is already hwpoisoned by AO action, process may not be
> killed, the process mapping this page may make a syscall include this
> page and result to trigger a VM_FAULT_HWPOISON fault, if it's in kernel
> mode it may be fixed by fixup
From: Arnd Bergmann
Building with 'make W=1' enables -Wpacked-not-aligned, and this
warns about pmcraid because of incompatible alignment constraints for
pmcraid_passthrough_ioctl_buffer:
drivers/scsi/pmcraid.h:1044:1: warning: alignment 1 of 'struct
pmcraid_passthrough_ioctl_buffer' is less th
Hello,
syzbot found the following issue on:
HEAD commit:d03154e8 Add linux-next specific files for 20210128
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=13a9591b50
kernel config: https://syzkaller.appspot.com/x/.config?x=6953ffb584722a1
dashboard l
On Mon, Feb 1, 2021 at 10:07 PM Greg KH wrote:
>
> On Mon, Feb 01, 2021 at 10:04:01PM +0530, Dwaipayan Ray wrote:
> > Hi,
> > on linux-next,
> > $ git log --pretty=format:"%h%x09%ad" | awk '$6>2021 {print $1}'
> > gives:
> > 4a2d78822fdf
> > 12ca45fea91c
> > 09f2724a786f
> >
> > These are patches
On Mon, Feb 1, 2021 at 7:47 AM Rob Clark wrote:
>
> On Mon, Feb 1, 2021 at 2:11 AM AngeloGioacchino Del Regno
> wrote:
> >
> > Il 31/01/21 20:50, Rob Clark ha scritto:
> > > On Sat, Jan 9, 2021 at 5:51 AM AngeloGioacchino Del Regno
> > > wrote:
> > >>
> > >> The VCO rate was being miscalculated
On Mon, Feb 01, 2021, Paolo Bonzini wrote:
> On 29/01/21 17:58, Sean Christopherson wrote:
> > On Fri, Jan 29, 2021, Paolo Bonzini wrote:
> > >*/
> > > if (!boot_cpu_has(X86_FEATURE_RTM))
> > > - data &= ~(ARCH_CAP_TAA_NO | ARCH_CAP_TSX_CTRL_MSR);
> > > + data
Jan Lübbe wrote:
> > > ... But at this point, you can still do 'keyctl read' on that key,
> > > exposing
> > > the key material to user space.
> >
> > I wonder if it would help to provide a keyctl function to mark a key as
> > being
> > permanently unreadable - so that it overrides the READ pe
Hello,
syzbot found the following issue on:
HEAD commit:fd821bf0 Add linux-next specific files for 20210201
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=11d8d0
kernel config: https://syzkaller.appspot.com/x/.config?x=80ac9f64e6e2c06
dashboard
Good day,
On Mon, Feb 01, 2021 at 09:02:44PM +0800, Qi Liu wrote:
> Remove duplicate included header files, as coresight-priv.h is included in
> these coresight drivers.
>
> Signed-off-by: Qi Liu
> ---
> drivers/hwtracing/coresight/coresight-catu.c | 2 --
> drivers/hwtracing/coresight/
On 2/1/21 1:14 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20210129:
>
still seeing this one:
on x86_64:
../drivers/gpu/drm/i915/i915_gem.c: In function ‘i915_gem_freeze_late’:
../drivers/gpu/drm/i915/i915_gem.c:1182:2: error: implicit declaration of
function ‘wbinvd_on_all_cpus’;
Hi John,
AFAIK, there is no such restrictions. Any queue can be used for
internal/external commands.
Regards,
Viswas G
> -Original Message-
> From: John Garry
> Sent: Monday, February 1, 2021 4:53 PM
> To: Viswas G - I30667 ; j...@linux.ibm.com;
> martin.peter...@oracle.com; akshat...
On Mon, Feb 1, 2021 at 7:17 AM Vlastimil Babka wrote:
>
> On 1/29/21 7:04 PM, Yang Shi wrote:
>
> >> > > @@ -209,9 +214,15 @@ static int expand_one_shrinker_info(struct
> >> > > mem_cgroup *memcg,
> >> > > if (!new)
> >> > > return -ENOMEM;
> >> > >
> >> > > -
Mickaël Salaün wrote:
> It doesn't contain Jarkko's Tested-by and Reviewed-by tags though.
I can add that in the merge.
David
On Mon, 1 Feb 2021 12:18:34 +1100
Alexey Kardashevskiy wrote:
> > Just curious, does the following patch fix it for v5?
>
>
> Yes it does!
Thanks for verifying.
>
>
> >
> > -- Steve
> >
> > diff --git a/kernel/tracepoint.c b/kernel/tracepoint.c
> > index 7261fa0f5e3c..cf3a6d104fdb 10064
On Thu, 2021-01-28 at 21:39 +1100, Herbert Xu wrote:
> Once they're distinct algorithms, we can then make sure that only
> the ones that are used in the kernel is added, even if some hardware
> may support more curves.
I like the idea of having different algorithms names (ecdh-nist-
pXXX) for diff
On 21-01-30 15:52:01, David Rientjes wrote:
> On Fri, 29 Jan 2021, Ben Widawsky wrote:
>
> > diff --git a/Documentation/ABI/testing/sysfs-bus-cxl
> > b/Documentation/ABI/testing/sysfs-bus-cxl
> > new file mode 100644
> > index ..fe7b87eba988
> > --- /dev/null
> > +++ b/Documentation/A
On Mon, Feb 1, 2021 at 10:20 PM Lukas Bulwahn wrote:
>
> On Mon, Feb 1, 2021 at 5:37 PM Greg KH wrote:
> >
> > On Mon, Feb 01, 2021 at 10:04:01PM +0530, Dwaipayan Ray wrote:
> > > Hi,
> > > on linux-next,
> > > $ git log --pretty=format:"%h%x09%ad" | awk '$6>2021 {print $1}'
> > > gives:
> > > 4a
months ago
config: sh-randconfig-s031-20210201 (attached as .config)
compiler: sh4-linux-gcc (GCC) 9.3.0
reproduce:
wget
https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O
~/bin/make.cross
chmod +x ~/bin/make.cross
# apt-get install sparse
On Mon, 1 Feb 2021 10:03:05 -0500, Pavel Tatashin wrote:
> This is against for-next/kexec, fix for sparse warning that was reported by
> kernel test robot [1].
>
> [1]
> https://lore.kernel.org/linux-arm-kernel/202101292143.c6tckvvx-...@intel.com
>
> Pavel Tatashin (1):
> arm64: hibernate: add
On Mon, Feb 01, 2021 at 01:15:29PM -0300, Vinicius Tinti wrote:
> On Mon, Feb 1, 2021 at 9:49 AM Christoph Hellwig wrote:
> >
> > DX_DEBUG is completely dead code, so either kill it off or make it an
> > actual CONFIG_* symbol through Kconfig if it seems useful.
>
> About the unreachable code in
On Mon, 1 Feb 2021 16:28:27 +
Max Gurtovoy wrote:
> This patch doesn't change any logic but only align to the concept of
> vfio_pci_core extensions. Extensions that are related to a platform
> and not to a specific vendor of PCI devices should be part of the core
> driver. Extensions that are
On Mon, Feb 1, 2021 at 9:05 AM Rob Clark wrote:
>
> On Mon, Feb 1, 2021 at 7:47 AM Rob Clark wrote:
> >
> > On Mon, Feb 1, 2021 at 2:11 AM AngeloGioacchino Del Regno
> > wrote:
> > >
> > > Il 31/01/21 20:50, Rob Clark ha scritto:
> > > > On Sat, Jan 9, 2021 at 5:51 AM AngeloGioacchino Del Regno
On Mon, Feb 1, 2021 at 2:54 AM Geert Uytterhoeven wrote:
>
> Hi Saravana,
>
> On Thu, Jan 28, 2021 at 6:08 PM Saravana Kannan wrote:
> > I already accounted for early clocks like this when I designed
> > fw_devlink. Each driver shouldn't need to set OF_POPULATED.
> > drivers/clk/clk.c already doe
On 01/02/2021 17:08, viswa...@microchip.com wrote:
Hi John,
AFAIK, there is no such restrictions. Any queue can be used for
internal/external commands.
ok, understood.
BTW, to see even more performance improvement, it would be good to use
request->tag for ccb tag, rather that the LLDD mana
On Sun, Jan 31, 2021 at 09:32:28PM -0700, Alex Williamson wrote:
> > I think we can leave common arch specific stuff, such as s390 (IIUC) in
> > the core driver. And only create vfio_pci drivers for
> > vendor/device/subvendor specific stuff.
>
> So on one hand you're telling us that the design
On Thu, Jan 28, 2021 at 06:23:29PM +0100, Maxime Ripard wrote:
> Hi,
Hi,
>
> On Sun, Jan 24, 2021 at 08:39:03PM +0100, Alexandre GRIVEAUX wrote:
> > Add Inet 86V Rev 2 support, based upon Inet 86VS.
> >
> > The Inet 86V use SL1536 touchpanel controller, the Inet 86VS a GSL1680,
> > which make the
Hi Keqian,
On 2/1/21 1:26 PM, Keqian Zhu wrote:
> Hi Eric,
>
> On 2020/11/18 19:21, Eric Auger wrote:
>> From: Jean-Philippe Brucker
>>
>> When handling faults from the event or PRI queue, we need to find the
>> struct device associated to a SID. Add a rb_tree to keep track of SIDs.
>>
>> Signed
Hi Keqian,
On 2/1/21 12:27 PM, Keqian Zhu wrote:
> Hi Eric,
>
> On 2020/11/18 19:21, Eric Auger wrote:
>> In virtualization use case, when a guest is assigned
>> a PCI host device, protected by a virtual IOMMU on the guest,
>> the physical IOMMU must be programmed to be consistent with
>> the gue
On Fri, 29 Jan 2021 16:24:25 -0800
Ben Widawsky wrote:
> From: Dan Williams
>
> The CXL.mem protocol allows a device to act as a provider of "System
> RAM" and/or "Persistent Memory" that is fully coherent as if the memory
> was attached to the typical CPU memory controller.
>
> With the CXL-2
On 2/1/21 11:52 AM, Cornelia Huck wrote:
On Mon, 1 Feb 2021 16:28:25 +
Max Gurtovoy wrote:
In case allocation fails, we must behave correctly and exit with error.
Signed-off-by: Max Gurtovoy
Fixes: e6b817d4b821 ("vfio-pci/zdev: Add zPCI capabilities to
VFIO_DEVICE_GET_INFO")
Reviewed
This feature is aimed at virtualized or containerized environments
where VM or container snapshotting duplicates memory state, which is a
challenge for applications that want to generate unique data such as
request IDs, UUIDs, and cryptographic nonces.
The patch set introduces a mechanism that pro
Hi Sven, Thierry, Uwe,
On Fri, Jan 29, 2021 at 05:16:51PM -0500, Sven Van Asbroeck wrote:
> Hi Clemens,
>
> On Fri, Jan 29, 2021 at 4:24 PM Sven Van Asbroeck wrote:
> >
> > LEN_ON = 409, LED_OFF = 1228 and
> > LED_ON = 419, LED_OFF = 1238
> > produce the same result. you can't see the difference
- Background
The VM Generation ID is a feature defined by Microsoft (paper:
http://go.microsoft.com/fwlink/?LinkId=260709) and supported by
multiple hypervisor vendors.
The feature can be used to drive the `sysgenid` mechanism required in
virtualized environments by software that works with local
- Background and problem
The System Generation ID feature is required in virtualized or
containerized environments by applications that work with local copies
or caches of world-unique data such as random values, uuids,
monotonically increasing counters, etc.
Such applications can be negatively af
On 2/1/21 11:28 AM, Max Gurtovoy wrote:
Zdev static functions does not use vdev argument. Remove it.
Signed-off-by: Max Gurtovoy
Huh. I must have dropped the use of vdev somewhere during review
versions. Thanks!
Reviewed-by: Matthew Rosato
@Alex/@Connie This one is just a cleanup and c
On Fri, Jan 08, 2021 at 12:15:01PM +, Quentin Perret wrote:
> From: Will Deacon
>
> We will soon need to synchronise multiple CPUs in the hyp text at EL2.
> The qspinlock-based locking used by the host is overkill for this purpose
> and relies on the kernel's "percpu" implementation for the M
If an error occurs starting a channel, don't "thaw" it.
We should assume the channel remains in a non-started state.
Update the comment in gsi_channel_stop(); calls to this function
are no longer retried.
Signed-off-by: Alex Elder
---
drivers/net/ipa/gsi.c | 6 --
1 file changed, 4 insertio
Create a new helper function that encapsulates issuing a set of
channel stop commands, retrying if appropriate, with a short delay
between attempts.
Signed-off-by: Alex Elder
---
drivers/net/ipa/gsi.c | 20 +++-
1 file changed, 15 insertions(+), 5 deletions(-)
diff --git a/drive
This is version 2 of a series that reworks the order in which things
happen during channel stop and suspend (and start and resume), in
order to address a hang that has been observed during suspend.
The introductory message on the first version of the series gave
some history which is omitted here.
Open-code gsi_channel_freeze() and gsi_channel_thaw() in all callers
and get rid of these two functions. This is part of reworking the
sequence of things done during channel suspend/resume and start/stop.
Signed-off-by: Alex Elder
---
drivers/net/ipa/gsi.c | 37 -
Create a new function that does most of the work of starting a
channel. What's different is that it takes a flag indicating
whether the channel should really be started or not. Create
another new function __gsi_channel_stop() that behaves similarly.
IPA v3.5.1 implements suspend using a special
On Mon, Feb 1, 2021 at 9:18 AM Rob Clark wrote:
>
> On Mon, Feb 1, 2021 at 9:05 AM Rob Clark wrote:
> >
> > On Mon, Feb 1, 2021 at 7:47 AM Rob Clark wrote:
> > >
> > > On Mon, Feb 1, 2021 at 2:11 AM AngeloGioacchino Del Regno
> > > wrote:
> > > >
> > > > Il 31/01/21 20:50, Rob Clark ha scritto:
On Mon, 1 Feb 2021 11:40:45 +0200
Max Gurtovoy wrote:
> On 2/1/2021 6:32 AM, Alex Williamson wrote:
> > On Sun, 31 Jan 2021 20:46:40 +0200
> > Max Gurtovoy wrote:
> >
> >> On 1/28/2021 11:02 PM, Alex Williamson wrote:
> >>> On Thu, 28 Jan 2021 17:29:30 +0100
> >>> Cornelia Huck wrote:
> >>>
Transactions to send data for a network device can be allocated at
any time up until the point the TX queue is stopped. It is possible
for ipa_start_xmit() to be called in one context just before a
the transmit queue is stopped in another.
Update gsi_channel_trans_last() so that for TX channels t
Disable both the I/O completion interrupt and NAPI polling on a
channel *after* we successfully stop it rather than before. This
ensures a completion occurring just before the channel is stopped
gets processed.
Enable NAPI polling and the interrupt *before* starting a channel
rather than after, t
On Mon, Feb 01, 2021 at 01:08:03PM +0100, Hermann Lauer wrote:
> On Thu, Jan 28, 2021 at 03:59:37PM +0100, Maxime Ripard wrote:
> > On Thu, Jan 28, 2021 at 12:18:42PM +0100, hermann.la...@uni-heidelberg.de
> > wrote:
> > > BPi Pro needs TX and RX delay for Gbit to work reliable and avoid high
> >
On 2021-02-01 4:22 a.m., Dan Carpenter wrote:
> Unlock before returning on this error path.
>
> Fixes: 111d746bb476 ("misc: bcm-vk: add VK messaging support")
> Signed-off-by: Dan Carpenter
> ---
> drivers/misc/bcm-vk/bcm_vk_msg.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> d
'--base' as documented in
https://git-scm.com/docs/git-format-patch]
url:
https://github.com/0day-ci/linux/commits/Wanpeng-Li/KVM-kvmclock-Fix-vCPUs-64-can-t-be-online-hotpluged/20210201-163927
base: https://git.kernel.org/pub/scm/virt/kvm/kvm.git linux-next
config: x86_64-randc
No completion interrupts will occur while an endpoint is suspended,
nor when a channel has been stopped for suspend. So there's no need
to disable the interrupt during suspend and re-enable it when
resuming. Without any interrupts occurring, there is no need to
disable/re-enable NAPI for channel
On 01/02/21 17:38, Sean Christopherson wrote:
/*
* On TAA affected systems:
* - nothing to do if TSX is disabled on the host.
* - we emulate TSX_CTRL if present on the host.
* This lets the guest use VERW to clear CPU buffers.
*/
it says "nothin
On Mon, 1 Feb 2021 at 17:50, Christoph Paasch
wrote:
> On Mon, Feb 1, 2021 at 8:09 AM Marco Elver wrote:
> >
> > Avoid the assumption that ksize(kmalloc(S)) == ksize(kmalloc(S)): when
> > cloning an skb, save and restore truesize after pskb_expand_head(). This
> > can occur if the allocator decid
> +cxl_mem-y := mem.o
> diff --git a/drivers/cxl/mem.c b/drivers/cxl/mem.c
> new file mode 100644
> index ..f4ee9a507ac9
> --- /dev/null
> +++ b/drivers/cxl/mem.c
> @@ -0,0 +1,61 @@
> +// SPDX-License-Identifier: GPL-2.0-only
> +/* Copyright(c) 2020 Intel Corporation. All rights reserve
On Mon, Feb 1, 2021 at 5:50 PM Bartosz Golaszewski
wrote:
>
> On Sat, Jan 30, 2021 at 4:45 AM quanyang.wang
> wrote:
> >
> > Hi Andy,
> >
> > On 1/30/21 1:26 AM, Andy Shevchenko wrote:
> > > On Fri, Jan 29, 2021 at 2:01 PM wrote:
> > >> From: Quanyang Wang
> > >>
> > >> In gpiochip_add_data_wit
On Mon, Feb 01, 2021, Paolo Bonzini wrote:
> On 01/02/21 17:38, Sean Christopherson wrote:
> > > > > /*
> > > > > * On TAA affected systems:
> > > > > * - nothing to do if TSX is disabled on the host.
> > > > > * - we emulate TSX_CTRL if present on the host.
> > > >
On Tue, Dec 15, 2020 at 3:57 AM SeongJae Park wrote:
>
> From: SeongJae Park
>
> Even somehow the initial monitoring target regions are well constructed
> to fulfill the assumption (pages in same region have similar access
> frequencies), the data access pattern can be dynamically changed. This
On Tue, Dec 15, 2020 at 3:59 AM SeongJae Park wrote:
>
> From: SeongJae Park
>
> DAMON is designed to be used by kernel space code such as the memory
> management subsystems, and therefore it provides only kernel space API.
Which kernel space APIs are being referred here?
> That said, letting t
>
> - return 0;
> + rc = -ENXIO;
> + for (i = regloc; i < regloc + 0x24; i += 8) {
This 0x24, 8, and
> + u32 reg_lo, reg_hi;
> + u8 reg_type;
> +
> + /* "register low and high" contain other bits */
> + pci_read_config_dword(pdev, i,
On Tue, Dec 15, 2020 at 3:56 AM SeongJae Park wrote:
>
> From: SeongJae Park
>
> To avoid the unbounded increase of the overhead, DAMON groups adjacent
> pages that assumed to have the same access frequencies into a region.
'that are assumed'
> As long as the assumption (pages in a region have
On Sat, Jan 30, 2021 at 8:39 AM carlis wrote:
> On Fri, 29 Jan 2021 16:26:12 +0200
> Andy Shevchenko wrote:
> > On Fri, Jan 29, 2021 at 3:56 PM carlis wrote:
> > > On Fri, 29 Jan 2021 12:23:08 +0200
> > > Andy Shevchenko wrote:
...
> > > Hi, I apologize for what I said in the previous two ema
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 1048ba83fb1c00cd24172e23e8263972f6b5d9ac
commit: 9f85cbe50aa044a46f0a22fda323fa27b80c82da RDMA/uverbs: Expose the new
GID query API to user space
date: 4 months ago
config: sh-randconfig-s031-20210201
On 31/01/2021 14:01, Leo Yan wrote:
> Option 1: by merging patches 07/08 and 08/08, we can firstly support PID
> tracing for root namespace, and later we can extend to support PID
> tracing in container (and in VMs).
>
> Option 2: we can use the software method to establish PID for SPE
> trace,
On Monday 01 Feb 2021 at 17:28:34 (+), Will Deacon wrote:
> On Fri, Jan 08, 2021 at 12:15:01PM +, Quentin Perret wrote:
> > From: Will Deacon
> >
> > We will soon need to synchronise multiple CPUs in the hyp text at EL2.
> > The qspinlock-based locking used by the host is overkill for thi
This patch avoids the indirect call for the common case:
ip_local_deliver and ip6_input
Signed-off-by: Brian Vazquez
---
include/net/dst.h | 6 +-
net/ipv4/ip_input.c | 1 +
2 files changed, 6 insertions(+), 1 deletion(-)
diff --git a/include/net/dst.h b/include/net/dst.h
index 10f0a83998
On Mon, Feb 1, 2021 at 8:27 AM Michal Simek wrote:
>
> The commit 3eb619b2f7d8 ("scripts/dtc: Update to upstream version
> v1.6.0-11-g9d7888cbf19c") updated dtc version which also contained DTC
> commit
> "81e0919a3e21 checks: Add interrupt provider test"
> where reasons for this checking are ment
This patch series uses the INDIRECT_CALL wrappers in some dst_ops
functions to mitigate retpoline costs. Benefits depend on the
platform as described below.
Background: The kernel rewrites the retpoline code at
__x86_indirect_thunk_r11 depending on the CPU's requirements.
The INDIRECT_CALL wrapper
On Fri, Jan 08, 2021 at 12:15:02PM +, Quentin Perret wrote:
> Move the initialization of kvm_nvhe_init_params in a dedicated function
> that is run early, and only once during KVM init, rather than every time
> the KVM vectors are set and reset.
>
> This also opens the opportunity for the hype
This patch avoids the indirect call for the common case:
ip6_dst_check and ipv4_dst_check
Signed-off-by: Brian Vazquez
---
include/net/dst.h | 7 ++-
net/core/sock.c | 12 ++--
net/ipv4/route.c| 7 +--
net/ipv4/tcp_ipv4.c | 5 -
net/ipv6/route.c| 7 +--
This patch avoids the indirect call for the common case:
ip6_mtu and ipv4_mtu
Signed-off-by: Brian Vazquez
---
include/net/dst.h | 4 +++-
net/ipv4/route.c | 6 --
net/ipv6/route.c | 6 --
3 files changed, 11 insertions(+), 5 deletions(-)
diff --git a/include/net/dst.h b/include/net/d
> +static int cxl_mem_setup_regs(struct cxl_mem *cxlm)
> +{
> + struct device *dev = &cxlm->pdev->dev;
> + int cap, cap_count;
> + u64 cap_array;
> +
> + cap_array = readq(cxlm->regs + CXLDEV_CAP_ARRAY_OFFSET);
> + if (CXL_GET_FIELD(cap_array, CXLDEV_CAP_ARRAY_ID) !=
> CXLDEV_C
There is a regular need in the kernel to provide a way to declare having
a dynamically sized set of trailing elements in a structure. Kernel code
should always use “flexible array members”[1] for these cases. The older
style of one-element or zero-length arrays should no longer be used[2].
Refacto
This patch avoids the indirect call for the common case:
ip6_output and ip_output
Signed-off-by: Brian Vazquez
---
include/net/dst.h | 8 +++-
net/ipv4/ip_output.c | 1 +
net/ipv6/ip6_output.c | 1 +
3 files changed, 9 insertions(+), 1 deletion(-)
diff --git a/include/net/dst.h b/inclu
From: Andrea Parri (Microsoft) Sent: Monday, February
1, 2021 6:48 AM
>
> If bit 22 of Group B Features is set, the guest has access to the
> Isolation Configuration CPUID leaf. On x86, the first four bits
> of EAX in this leaf provide the isolation type of the partition;
> we entail three isol
From: Andrea Parri (Microsoft) Sent: Monday, February
1, 2021 6:48 AM
>
> Only the VSCs or ICs that have been hardened and that are critical for
> the successful adoption of Confidential VMs should be allowed if the
> guest is running isolated. This change reduces the footprint of the
> code th
On Fri, Jan 08, 2021 at 12:15:03PM +, Quentin Perret wrote:
> Currently, the KVM page-table allocator uses a mix of put_page() and
> free_page() calls depending on the context even though page-allocation
> is always achieved using variants of __get_free_page().
>
> Make the code consitent by u
On Thu, Jan 28, 2021 at 6:35 AM Sumit Semwal wrote:
>
> Hi Simon,
>
> On Thu, 28 Jan 2021 at 20:01, Simon Ser wrote:
> >
> > On Thursday, January 28th, 2021 at 1:03 PM, Sumit Semwal
> > wrote:
> >
> > > Since he didn't comment over Hridya's last clarification about the
> > > tracepoints to trac
Somehow I forgot about this problem. Let me resend the last version
based on discussion with Linus. IIRC he was agree with this series.
And let me remind why 3/4 temporary adds the "transient" TS_COMPAT_RESTART
flag killed by the next patch: to simplify the backporting. 1-3 can fix
the problem wit
Preparation. Add the new helper which sets restart_block->fn and calls
the dummy arch_set_restart_data() helper.
Signed-off-by: Oleg Nesterov
---
fs/select.c| 10 --
include/linux/thread_info.h| 13 +
kernel/futex.c | 3 +--
kernel/tim
From: Andrea Parri (Microsoft) Sent: Monday, February
1, 2021 6:48 AM
>
> Restrict the protocol version(s) that will be negotiated with the host
> to be 5.2 or greater if the guest is running isolated. This reduces the
> footprint of the code that will be exercised by Confidential VMs and
> hen
The comment in get_nr_restart_syscall() says:
* The problem is that we can get here when ptrace pokes
* syscall-like values into regs even if we're not in a syscall
* at all.
Yes. but if we are not in syscall then the
status & (TS_COMPAT|TS_I386_REGS_POKED)
ch
With this patch x86 just saves current_thread_info()->status in the
new restart_block->arch_data field, TS_COMPAT_RESTART can be removed.
Rather than saving "status" we could shift the code from
get_nr_restart_syscall() to arch_set_restart_data() and save the syscall
number in ->arch_data.
Signed
Move TS_COMPAT back to asm/thread_info.h, close to TS_I386_REGS_POKED.
It was moved to asm/processor.h by b9d989c7218a ("x86/asm: Move the
thread_info::status field to thread_struct"), then later 37a8f7c38339
("x86/asm: Move 'status' from thread_struct to thread_info") moved the
'status' field bac
From: Andrea Parri (Microsoft) Sent: Monday, February
1, 2021 6:48 AM
>
> Restrict the NVSP protocol version(s) that will be negotiated with the
> host to be NVSP_PROTOCOL_VERSION_61 or greater if the guest is running
> isolated. Moreover, do not advertise the SR-IOV capability and ignore
> NVS
On 1/30/21 5:19 PM, David Rientjes wrote:
> On Mon, 25 Jan 2021, Dave Hansen wrote:
>
>> diff -puN mm/migrate.c~0006-node-Define-and-export-memory-migration-path
>> mm/migrate.c
>> --- a/mm/migrate.c~0006-node-Define-and-export-memory-migration-path
>> 2021-01-25 16:23:09.553866709 -0800
>> +++
On 2/1/21 12:14 PM, Cornelia Huck wrote:
On Mon, 1 Feb 2021 16:28:27 +
Max Gurtovoy wrote:
This patch doesn't change any logic but only align to the concept of
vfio_pci_core extensions. Extensions that are related to a platform
and not to a specific vendor of PCI devices should be part of
On 21-02-01 12:41:36, Konrad Rzeszutek Wilk wrote:
> > +static int cxl_mem_setup_regs(struct cxl_mem *cxlm)
> > +{
> > + struct device *dev = &cxlm->pdev->dev;
> > + int cap, cap_count;
> > + u64 cap_array;
> > +
> > + cap_array = readq(cxlm->regs + CXLDEV_CAP_ARRAY_OFFSET);
> > + if (CXL
On 2/1/21 8:51 AM, Bert Vermeulen wrote:
> On 2/1/21 12:17 PM, Bhaskar Chowdhury wrote:
>> s/debugees/debuge's/
>
> Definitely not.
>
and preferably "inter-CPU".
--
~Randy
netiquette: https://people.kernel.org/tglx/notes-about-netiquette
On Fri, Jan 29, 2021 at 07:41:27AM -0800, Alex Belits wrote:
> On 1/28/21 07:56, Thomas Gleixner wrote:
> > External Email
> >
> > --
> > On Wed, Jan 27 2021 at 10:09, Marcelo Tosatti wrote:
> > > On Wed, Jan 27, 2021 at 12:36:30P
701 - 800 of 1492 matches
Mail list logo
