Rework calibrate function to use common function. Derive the offset from
a missing hardcoded slope table and the data from the nvmem calib
efuses.
Drop custom get_temp function and use generic api.
Signed-off-by: Ansuel Smith
Acked-by: Thara Gopinath
---
drivers/thermal/qcom/tsens-8960.c | 56 +
Device based on tsens VER_0 contains a hardware bug that results in some
problem with sensor enablement. Sensor id 6-11 can't be enabled
selectively and all of them must be enabled in one step.
Signed-off-by: Ansuel Smith
---
drivers/thermal/qcom/tsens-8960.c | 24 +---
1 fil
Use init_common and drop custom init for msm8960.
Signed-off-by: Ansuel Smith
Reviewed-by: Thara Gopinath
---
drivers/thermal/qcom/tsens-8960.c | 52 +--
1 file changed, 1 insertion(+), 51 deletions(-)
diff --git a/drivers/thermal/qcom/tsens-8960.c
b/drivers/therma
Function compute_intercept_slope hardcode the sensor slope to
SLOPE_DEFAULT. Change this and use the default value only if a slope is
not defined. This is needed for tsens VER_0 that has a hardcoded slope
table.
Signed-off-by: Ansuel Smith
Reviewed-by: Thara Gopinath
---
drivers/thermal/qcom/ts
VER_0 is used to describe device based on tsens version before v0.1.
These device are devices based on msm8960 for example apq8064 or
ipq806x.
Signed-off-by: Ansuel Smith
---
drivers/thermal/qcom/tsens.c | 141 ---
drivers/thermal/qcom/tsens.h | 4 +-
2 files ch
This patchset convert msm8960 to reg_filed, use int_common instead
of a custom function and fix wrong tsens get_temp function for msm8960.
Ipq8064 SoCs tsens driver is based on 8960 tsens driver. Ipq8064 needs
to be registered as a gcc child as the tsens regs on this platform are
shared with the c
From: Zi Yan
We did not have a direct user interface of splitting the compound page
backing a THP and there is no need unless we want to expose the THP
implementation details to users. Make /split_huge_pages accept
a new command to do that.
By writing ",," to
/split_huge_pages, THPs within the g
From: Zi Yan
Further extend /split_huge_pages to accept
",," for file-backed THP split tests since
tmpfs may have file backed by THP that mapped nowhere.
Update selftest program to test file-backed THP split too.
Suggested-by: Kirill A. Shutemov
Signed-off-by: Zi Yan
---
mm/huge_memory.c
On 3/18/2021 4:35 PM, Robin Murphy wrote:
> On 2021-03-18 21:31, Florian Fainelli wrote:
>>
>>
>> On 3/18/2021 12:53 PM, Robin Murphy wrote:
>>> On 2021-03-18 19:43, Florian Fainelli wrote:
On 3/18/2021 12:34 PM, Robin Murphy wrote:
> On 2021-03-18 19:22, Florian Fainelli wrot
From: Liu xuzhi
A typo is found out by codespell tool in 251th lines of cifs_swn.c:
$ codespell ./fs/cifs/
./cifs_swn.c:251: funciton ==> function
Fix a typo found by codespell.
Signed-off-by: Liu xuzhi
---
fs/cifs/cifs_swn.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On 3/18/21 7:53 PM, Shenming Lu wrote:
On 2021/3/18 17:07, Tian, Kevin wrote:
From: Shenming Lu
Sent: Thursday, March 18, 2021 3:53 PM
On 2021/2/4 14:52, Tian, Kevin wrote:>>> In reality, many
devices allow I/O faulting only in selective contexts. However, there
is no standard way (e.g. PCISI
O Sat, Mar 13, 2021 at 07:15:54PM +, Jonathan Cameron wrote:
> On Tue, 9 Mar 2021 01:17:15 +
> Joe Sandom wrote:
>
> > Driver implementation for AMS/TAOS tsl2591 ambient light sensor.
> >
> > This driver supports configuration via device tree and sysfs.
> > Supported channels for raw in
On 3/18/2021 12:16 PM, Adrian Hunter wrote:
On 18/03/21 7:58 pm, Asutosh Das (asd) wrote:
On 3/18/2021 10:54 AM, Rafael J. Wysocki wrote:
On Thu, Mar 18, 2021 at 6:33 PM Asutosh Das (asd)
wrote:
On 3/18/2021 7:00 AM, Rafael J. Wysocki wrote:
On Wed, Mar 17, 2021 at 7:37 AM Adrian Hunter wr
Resumes the actual scsi device the unit descriptor of which
is being accessed instead of the hba alone.
Reviewed-by: Can Guo
Signed-off-by: Asutosh Das
---
drivers/scsi/ufs/ufs-sysfs.c | 30 +-
1 file changed, 17 insertions(+), 13 deletions(-)
diff --git a/drivers/s
During runtime-suspend of ufs host, the scsi devices are
already suspended and so are the queues associated with them.
But the ufs host sends SSU to wlun during its runtime-suspend.
During the process blk_queue_enter checks if the queue is not in
suspended state. If so, it waits for the queue to re
Hi Joerg,
On 3/18/21 5:12 PM, Joerg Roedel wrote:
Hi,
On Mon, Mar 08, 2021 at 11:47:46AM -0800, Raj, Ashok wrote:
That is the primary motivation, given that we have moved to 1st level for
general IOVA, first level doesn't have a WO mapping. I didn't know enough
about the history to determine i
From: Liu xuzhi
A typo is found out by codespell tool in 1107th lines of super.c:
$ codespell ./fs/ext2/
./super.c:1107: fileystem ==> filesystem
Fix a typo found by codespell.
Signed-off-by: Liu xuzhi
---
fs/ext2/super.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/f
Hi Jacopo,
On Wed, Mar 17, 2021 at 11:04:45AM +0100, Jacopo Mondi wrote:
> On Mon, Mar 15, 2021 at 05:22:37PM +, Kieran Bingham wrote:
> > On 15/03/2021 13:15, Jacopo Mondi wrote:
> > > It has been observed through repeated testing (250 boots) that in the
> > > 10% of the cases the RDACM21 ini
On 3/18/21 4:56 PM, Tian, Kevin wrote:
From: Longpeng (Mike, Cloud Infrastructure Service Product Dept.)
-Original Message-
From: Tian, Kevin [mailto:kevin.t...@intel.com]
Sent: Thursday, March 18, 2021 4:27 PM
To: Longpeng (Mike, Cloud Infrastructure Service Product Dept.)
; Nadav Ami
From: Dragos Rosioru
This patch aims to enable PM support in the DCP driver.
The values for DCP Control and Channel Control registers had to be saved
and restored due to the fact that the DCP block would remain in a
low-power mode and have its clocks gated after suspend/resume cycles.
A simple t
From: Dragos Rosioru
Added suspend/resume operations for PM support in the DCP driver.
After a suspend/resume cycle DCP would still be in a low-power mode
and have its clocks gated, thus requiring state to be saved beforehand:
- Control register value(DCP_CTRL)
- Channel control register value(DC
> On Mar 18, 2021, at 5:09 PM, Arnaldo wrote:
>
>
>
> On March 18, 2021 6:14:34 PM GMT-03:00, Jiri Olsa wrote:
>> On Thu, Mar 18, 2021 at 03:52:51AM +, Song Liu wrote:
>>>
>>>
On Mar 17, 2021, at 6:11 AM, Arnaldo Carvalho de Melo
>> wrote:
Em Wed, Mar 17, 2021 at 02:2
Hi Jean,
Slightly off the title. As we are moving to use cgroup to limit PASID
allocations, it would be much simpler if we enforce on the current task.
However, iommu_sva_alloc_pasid() takes an mm_struct pointer as argument
which implies it can be something other the the current task mm. So far a
On Thu, Mar 18, 2021 at 12:38:42PM -0500, Josh Poimboeuf wrote:
> On Thu, Mar 18, 2021 at 06:04:25PM +0100, Peter Zijlstra wrote:
> > On Thu, Mar 18, 2021 at 11:36:40AM -0500, Josh Poimboeuf wrote:
> > > > I was thinking you could get a section changed without touching
> > > > relocations, but whil
Hi all,
Today's linux-next merge of the net-next tree got a conflict in:
kernel/bpf/verifier.c
between commits:
b5871dca250c ("bpf: Simplify alu_limit masking for pointer arithmetic")
1b1597e64e1a ("bpf: Add sanity check for upper ptr_limit")
from the net tree and commit:
69c087ba6225
On Thu, Mar 18, 2021 at 04:36:08PM -0700, Guenter Roeck wrote:
> On Thu, Mar 18, 2021 at 08:15:06PM -0300, Jonas Malaco wrote:
>
> [ ... ]
>
> > > Either case, the spinlocks are overkill. It would be much easier to
> > > convert raw readings here into temperature and fan speed and store
> > > the
isspace() could be vulnerable in terms of unpredictable results. So, the
parameter of the isspace() should be cast with 'unsigned int'. We found out
that information through these sites. (Microsoft, Stack Overflow)
url: [https://docs.microsoft.com/en-us/cpp/code-quality/c6328?view=msvc-160]
url:
On Thu, 18 Mar 2021, Christoph Hellwig wrote:
> sb1250_swarm_defconfig enables CONFIG_IDE but no actual host controller
> driver, so just drop CONFIG_IDE, CONFIG_BLK_DEV_IDECD and
> CONFIG_BLK_DEV_IDETAPE as they are useless.
Actually BLK_DEV_PLATFORM would handle the SWARM's platform driver as
On March 18, 2021 6:14:34 PM GMT-03:00, Jiri Olsa wrote:
>On Thu, Mar 18, 2021 at 03:52:51AM +, Song Liu wrote:
>>
>>
>> > On Mar 17, 2021, at 6:11 AM, Arnaldo Carvalho de Melo
> wrote:
>> >
>> > Em Wed, Mar 17, 2021 at 02:29:28PM +0900, Namhyung Kim escreveu:
>> >> Hi Song,
>> >>
>> >>
GDB produces the following warning when debugging kernels built with
CONFIG_RELR:
BFD: /android0/linux-next/vmlinux: unknown type [0x13] section `.relr.dyn'
when loading a kernel built with CONFIG_RELR into GDB. It can also
prevent debugging symbols using such relocations.
Peter sugguests:
[Th
On Thu, 18 Mar 2021 14:38:53 -0400
Tony Krowiak wrote:
> On 3/17/21 7:17 PM, Halil Pasic wrote:
> > On Wed, 10 Mar 2021 10:05:59 -0500
> > Tony Krowiak wrote:
> >
> >> - ret = vfio_ap_mdev_reset_queues(mdev);
> >> + matrix_mdev = mdev_get_drvdata(mdev);
> > Is it guaranteed
On Fri, Mar 05, 2021 at 04:18:37AM +, Matthew Wilcox (Oracle) wrote:
> A struct folio refers to an entire (possibly compound) page. A function
> which takes a struct folio argument declares that it will operate on the
> entire compound page, not just PAGE_SIZE bytes. In return, the caller
> g
From: Mark Rutland
commit 3f618ab3323407ee4c6a6734a37eb6e9663ebfb9 upstream.
When building with KASAN and LKDTM, clang may implictly generate an
asan.module_ctor function in the LKDTM rodata object. The Makefile moves
the lkdtm_rodata_do_nothing() function into .rodata by renaming the
file's .te
From: Thomas Gleixner
commit 655389433e7efec589838b400a2a652b3ffa upstream.
Some code pathes, especially the low level entry code, must be protected
against instrumentation for various reasons:
- Low level entry code can be a fragile beast, especially on x86.
- With NO_HZ_FULL RCU state
Backport 2 patches that are required to make KASAN+LKDTM work
with recent clang (patch 2/2 has a complete description).
Tested on our chromeos-4.19 branch.
Patch 1/2 is context conflict only, and 2/2 is a clean backport.
These patches have been merged to 5.4 stable already. We might
need to bac
On Thu, Mar 18, 2021 at 3:29 PM Peter Zijlstra wrote:
>
> On Thu, Mar 18, 2021 at 10:10:55AM -0700, Sami Tolvanen wrote:
> > +static void update_shadow(struct module *mod, unsigned long base_addr,
> > + update_shadow_fn fn)
> > +{
> > + struct cfi_shadow *prev;
> > + struct cfi
Hello,
There is a suspend failure on mt8173 chromebooks that use this timer.
The failure shows as an errno: -95 failure with none device.
I tracked this down to the arm trusted firmware aborting the suspend
due to this timer having a pending IRQ, due to not being disabled
during suspend / clockev
On Thu, 18 Mar 2021 10:00:17 -0600 Jens Axboe wrote:
> On 3/18/21 9:53 AM, Shakeel Butt wrote:
> > On Wed, Mar 17, 2021 at 3:30 PM Jens Axboe wrote:
> >>
> >> On 3/16/21 9:36 AM, Dan Schatzberg wrote:
> >>> No major changes, just rebasing and resubmitting
> >>
> >> Applied for 5.13, thanks.
> >>
-20210318 (attached as .config)
compiler: powerpc64-linux-gcc (GCC) 9.3.0
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot
cocci warnings: (new ones prefixed by >>)
>> arch/powerpc/kernel/iommu.c:76:2-16: WARNING: NULL check before some freeing
From: kernel test robot
arch/powerpc/kernel/iommu.c:76:2-16: WARNING: NULL check before some freeing
functions is not needed.
NULL check before some freeing functions is not needed.
Based on checkpatch warning
"kfree(NULL) is safe this check is probably not required"
and kfreeaddr.cocci by
(CC: Will and ARM ML)
On Fri, Mar 19, 2021 at 6:14 AM Nathan Chancellor wrote:
>
> On Sun, Feb 28, 2021 at 03:10:28PM +0900, Masahiro Yamada wrote:
> > Since commit f2f02ebd8f38 ("kbuild: improve cc-option to clean up all
> > temporary files"), running 'make kernelversion' in a read-only source
On Thu, Mar 18, 2021 at 08:15:06PM -0300, Jonas Malaco wrote:
[ ... ]
> > Either case, the spinlocks are overkill. It would be much easier to
> > convert raw readings here into temperature and fan speed and store
> > the resulting values in struct kraken2_priv_data, and then to
> > just report it
On 2021-03-18 21:31, Florian Fainelli wrote:
On 3/18/2021 12:53 PM, Robin Murphy wrote:
On 2021-03-18 19:43, Florian Fainelli wrote:
On 3/18/2021 12:34 PM, Robin Murphy wrote:
On 2021-03-18 19:22, Florian Fainelli wrote:
On 3/18/2021 12:18 PM, Florian Fainelli wrote:
It may be useful t
s/verfied/verified/
Signed-off-by: Bhaskar Chowdhury
---
tools/testing/selftests/net/forwarding/fib_offload_lib.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/testing/selftests/net/forwarding/fib_offload_lib.sh
b/tools/testing/selftests/net/forwarding/fib_offload_l
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Thu, 18 Mar 2021 13:59:26 -0500 you wrote:
> There is currently a configuration dependency that restricts IPA to
> be supported only on 64-bit machines. There are only a few things
> that really require that, and those
I've queued this patchset here:
git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git
landlock_lsm
and pulled it into next-testing, which will get it coverage in linux-next.
All going well, I'll aim to push this to Linus in the next merge window.
More review and testing duri
On 3/18/21 5:16 PM, Stephen Rothwell wrote:
> Hi all,
>
> Commit
>
> c2c6c067c050 ("io_uring: remove structures from include/linux/io_uring.h")
>
> is missing a Signed-off-by from its author.
Stefan, let me know if you're OK with me adding that, not sure how I missed
that.
--
Jens Axboe
Hi Parshuram,
Thank you for the patch.
On Thu, Mar 18, 2021 at 07:45:30AM +0100, Parshuram Thombare wrote:
> Add binding changes for HDCP in the MHDP8546 DPI/DP bridge binding.
>
> Signed-off-by: Parshuram Thombare
> ---
> .../display/bridge/cdns,mhdp8546.yaml | 24 +++
Hi Arnd,
On Thu, 18 Mar 2021 23:55:48 +0100 Arnd Bergmann wrote:
>
> Sorry for the delay. I had cleaned out the old branches while updating to -rc2
> and forgot to upload the new fixes. I just pushed the branch with the latest
> fixes.
No problem, I assumed that if you had any urgent fixes, you
s/proces/process/
Signed-off-by: Bhaskar Chowdhury
---
drivers/gpu/drm/amd/amdgpu/psp_v11_0.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/amd/amdgpu/psp_v11_0.c
b/drivers/gpu/drm/amd/amdgpu/psp_v11_0.c
index bf3857867f51..c1d5a3085bae 100644
--- a/drive
From: Vladimir Oltean
The DSA core has a layered structure, and even though we end up
returning 0 (success) to user space when setting a bonding/team upper
that can't be offloaded, some parts of the framework actually need to
know that we couldn't offload that.
For example, if dsa_switch_lag_joi
From: Vladimir Oltean
On reception of an skb, the bridge checks if it was marked as 'already
forwarded in hardware' (checks if skb->offload_fwd_mark == 1), and if it
is, it puts a mark of its own on that skb, with the switchdev mark of
the ingress port. Then during forwarding, it enforces that th
From: Vladimir Oltean
DSA has gained the recent ability to deal gracefully with upper
interfaces it cannot offload, such as the bridge, bonding or team
drivers. When such uppers exist, the ports are still in standalone mode
as far as the hardware is concerned.
But when we deliver packets to the
From: Vladimir Oltean
Similar to the DSA situation, ocelot supports LAG offload but treats
this scenario improperly:
ip link add br0 type bridge
ip link add bond0 type bond
ip link set bond0 master br0
ip link set swp0 master bond0
We do the same thing as we do there, which is to simulate a 'br
From: Vladimir Oltean
The premise of this change is that the switchdev port attributes and
objects offloaded by ocelot might have been missed when we are joining
an already existing bridge port, such as a bonding interface.
The patch pulls these switchdev attributes and objects from the bridge,
From: Vladimir Oltean
The ocelot switches are a bit odd in that they do not have an STP state
to put the ports into. Instead, the forwarding configuration is delayed
from the typical port_bridge_join into stp_state_set, when the port enters
the BR_STATE_FORWARDING state.
I can only guess that th
From: Vladimir Oltean
Currently this simple setup:
ip link add br0 type bridge vlan_filtering 1
ip link add bond0 type bond
ip link set bond0 master br0
ip link set swp0 master bond0
will not work because the bridge has created the PVID in br_add_if ->
nbp_vlan_init, and it has notified switchd
From: Vladimir Oltean
I have udhcpcd in my system and this is configured to bring interfaces
up as soon as they are created.
I create a bridge as follows:
ip link add br0 type bridge
As soon as I create the bridge and udhcpcd brings it up, I have some
other crap (avahi) that starts sending som
From: Vladimir Oltean
When a DSA port joins a LAG that already had an FDB entry pointing to it:
ip link set bond0 master br0
bridge fdb add dev bond0 00:01:02:03:04:05 master static
ip link set swp0 master bond0
the DSA port will have no idea that this FDB entry is there, because it
missed the
From: Vladimir Oltean
The SWITCHDEV_ATTR_ID_BRIDGE_AGEING_TIME attribute is only emitted from:
sysfs/ioctl/netlink
-> br_set_ageing_time
-> __set_ageing_time
therefore not at bridge port creation time, so:
(a) drivers had to hardcode the initial value for the address ageing time,
because
From: Vladimir Oltean
Make sure that the multicast router setting of the bridge is picked up
correctly by DSA when joining, regardless of whether there are
sandwiched interfaces or not. The SWITCHDEV_ATTR_ID_BRIDGE_MROUTER port
attribute is only emitted from br_mc_router_state_change.
Signed-off
From: Vladimir Oltean
This is the same situation as for other switchdev port attributes: if we
join an already-created bridge port, such as a bond master interface,
then we can miss the initial switchdev notification emitted by the
bridge for this port.
Signed-off-by: Vladimir Oltean
---
net/d
From: Vladimir Oltean
It may happen that we have the following topology:
ip link add br0 type bridge stp_state 1
ip link add bond0 type bond
ip link set bond0 master br0
ip link set swp0 master bond0
ip link set swp1 master bond0
STP decides that it should put bond0 into the BLOCKING state, and
From: Vladimir Oltean
DSA currently assumes that the bridge port starts off with this
constellation of bridge port flags:
- learning on
- unicast flooding on
- multicast flooding on
- broadcast flooding on
just by virtue of code copy-pasta from the bridge layer (new_nbp).
This was a simple enou
From: Vladimir Oltean
This is a pretty noisy change that was broken out of the larger change
for replaying switchdev attributes and objects at bridge join time,
which is when these extack objects are actually used.
Signed-off-by: Vladimir Oltean
---
net/dsa/dsa_priv.h | 6 --
net/dsa/port.
From: Vladimir Oltean
DSA can properly detect and offload this sequence of operations:
ip link add br0 type bridge
ip link add bond0 type bond
ip link set swp0 master bond0
ip link set bond0 master br0
But not this one:
ip link add br0 type bridge
ip link add bond0 type bond
ip link set bond0
From: Vladimir Oltean
This series has two objectives:
- To make LAG uppers on top of DSA ports work regardless of which order
we link interfaces to their masters (first make the port join the LAG,
then the LAG join the bridge, or the other way around).
- To make DSA ports support non-offloade
Hi all,
Commit
c2c6c067c050 ("io_uring: remove structures from include/linux/io_uring.h")
is missing a Signed-off-by from its author.
--
Cheers,
Stephen Rothwell
pgppGfflW2SsR.pgp
Description: OpenPGP digital signature
On Thu, Mar 18, 2021 at 11:55:39AM -0700, Guenter Roeck wrote:
> On 3/18/21 9:48 AM, Jonas Malaco wrote:
> > These are "all-in-one" CPU liquid coolers that can be monitored and
> > controlled through a proprietary USB HID protocol.
> >
> > While the models have differently sized radiators and come
> This commit adds a minimal set of supported filesystem access-control
> which doesn't enable to restrict all file-related actions.
It would be great to get some more review/acks on this patch, particularly
from VFS/FS folk.
--
James Morris
On Wed, Mar 17, 2021 at 02:44:41PM +0100, Thomas Gleixner wrote:
> On Tue, Mar 16 2021 at 00:37, Ira Weiny wrote:
> >
> > I think I see the issue. I think this is an invalid configuration.
> >
> > 00:26:43 > grep DEBUG_KMAP config-5.11.0-rc7-2-g61b205f57991
> > CONFIG_DEBUG_KMAP_LOCAL=y
> > C
From: Ira Weiny
The kernel test robot found that __kmap_local_sched_out() was not
correctly skipping the guard pages when
CONFIG_DEBUG_KMAP_LOCAL_FORCE_MAP was set.[1] This was due to
CONFIG_DEBUG_HIGHMEM check being used.
Change the configuration check to be correct.
[1] https://lore.kernel.o
Hi John,
On Thu, Mar 18, 2021 at 9:19 AM John Garry wrote:
>
> On 18/03/2021 00:24, Jolly Shah wrote:
> > Hi John,
> >
> > Thanks for the review.
> >
> >
> > On Wed, Mar 17, 2021 at 4:44 AM John Garry wrote:
> >>
> >> On 16/03/2021 19:39, Jolly Shah wrote:
> >>> When the cache_type for the scsi
On 3/18/21 2:24 PM, Erik Rosen wrote:
> Add support for TI TPS53676 controller to the tps53679 pmbus driver
>
> The driver uses the USER_DATA_03 register to figure out how many phases are
> enabled and to which channel they are assigned, and sets the number of pages
checkpatch complains about the
Found this while trying to make some changes to the kms_cursor_crc test.
curs507a_acquire checks that the width and height of the cursor framebuffer
are equal (asyw->image.{w,h}). This isn't entirely correct though, as the
height of the cursor can be larger than the size of the cursor, as long as
t
allmodconfig
powerpc allnoconfig
i386 randconfig-a001-20210318
i386 randconfig-a005-20210318
i386 randconfig-a003-20210318
i386 randconfig-a002-20210318
i386 randconfig-a006-20210318
i386
allyesconfig
mips allmodconfig
powerpc allyesconfig
powerpc allmodconfig
powerpc allnoconfig
i386 randconfig-a001-20210318
i386 randconfig-a005-20210318
i386
When the cache_type for the scsi device is changed, the scsi layer
issues a MODE_SELECT command. The caching mode details are communicated
via a request buffer associated with the scsi command with data
direction set as DMA_TO_DEVICE (scsi_mode_select). When this command
reaches the libata layer, a
On Mon, Mar 15, 2021 at 10:43 PM Stephen Rothwell wrote:
>
> Hi all,
>
> On Mon, 8 Mar 2021 18:57:41 +1100 Stephen Rothwell
> wrote:
> >
> > Fetching the arm-soc-fixes tree
> > (git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc.git#arm/fixes)
> > produces this error:
> >
> > fatal: couldn't
Use my personal email, the @google.com one will stop functioning soon.
Signed-off-by: Andrey Konovalov
---
.mailmap | 1 +
1 file changed, 1 insertion(+)
diff --git a/.mailmap b/.mailmap
index 85b93cdefc87..11219fa3b62b 100644
--- a/.mailmap
+++ b/.mailmap
@@ -36,6 +36,7 @@ Andrew Morton
Andr
Add builder macros to generate the MSR bitmap helpers to reduce the
amount of copy-paste code, especially with respect to all the magic
numbers needed to calc the correct bit location.
No functional change intended.
Signed-off-by: Sean Christopherson
---
arch/x86/kvm/vmx/vmx.h | 77 ++--
Always check vmcs01's MSR bitmap when merging L0 and L1 bitmaps for L2,
and always update the relevant bits in vmcs02. This fixes two distinct,
but intertwined bugs related to dynamic MSR bitmap modifications.
The first issue is that KVM fails to enable MSR interception in vmcs02
for the FS/GS ba
Clean up the x2APIC MSR bitmap intereption code for L2, which is the last
holdout of open coded bitmap manipulations. Freshen up the SDM/PRM
comment, rename the function to make it abundantly clear the funky
behavior is x2APIC specific, and explain _why_ vmcs01's bitmap is ignored
(the previous co
Fix a plethora of issues with MSR filtering by installing the resulting
filter as an atomic bundle instead of updating the live filter one range
at a time. The KVM_X86_SET_MSR_FILTER ioctl() isn't truly atomic, as
the hardware MSR bitmaps won't be updated until the next VM-Enter, but
the relevant
Rework the MSR filtering implementation to treat a given filter instance
as an atomic unit, and to properly protect it with SRCU.
Fix two nVMX bugs related to MSR filtering (one directly, one indirectly),
and additional cleanup on top.
Regarding the macro insanity in patch 03, I verified the befo
On Thu, 2021-03-18 at 18:13 -0400, Ilia Mirkin wrote:
> On Thu, Mar 18, 2021 at 5:56 PM Lyude Paul wrote:
> >
> > Found this while trying to make some changes to the kms_cursor_crc test.
> > curs507a_acquire checks that the width and height of the cursor framebuffer
> > are equal (asyw->image.{w,
On 15/1/21 11:33 pm, Mark Rutland wrote:
> On Thu, Jan 14, 2021 at 04:07:55PM -0600, Madhavan T. Venkataraman wrote:
>> Hi all,
>>
>> My name is Madhavan Venkataraman.
>
> Hi Madhavan,
>
>> Microsoft is very interested in Live Patching support for ARM64.
>> On behalf of Microsoft, I would like to
On Thu, Mar 18, 2021 at 10:10:55AM -0700, Sami Tolvanen wrote:
> +static void update_shadow(struct module *mod, unsigned long base_addr,
> + update_shadow_fn fn)
> +{
> + struct cfi_shadow *prev;
> + struct cfi_shadow *next;
> + unsigned long min_addr, max_addr;
> +
> +
Hi Alexander,
I love your patch! Perhaps something to improve:
[auto build test WARNING on gpio/for-next]
[also build test WARNING on v5.12-rc3 next-20210318]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--bas
On 3/18/21 12:40 PM, Mark Brown wrote:
> On Mon, Mar 15, 2021 at 11:57:54AM -0500, madve...@linux.microsoft.com wrote:
>
>> To summarize, pt_regs->stackframe is used (or will be used) as a marker
>> frame in stack traces. To enable the unwinder to detect these frames, tag
>> each pt_regs->stack
Hi Alexander,
I love your patch! Yet something to improve:
[auto build test ERROR on gpio/for-next]
[also build test ERROR on v5.12-rc3 next-20210318]
[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 doc
On Thu, Mar 18, 2021 at 5:56 PM Lyude Paul wrote:
>
> Found this while trying to make some changes to the kms_cursor_crc test.
> curs507a_acquire checks that the width and height of the cursor framebuffer
> are equal (asyw->image.{w,h}). This is actually wrong though, as we only
> want to be conce
The following commit has been merged into the x86/seves branch of tip:
Commit-ID: e927e62d8e370ebfc0d702fec22bc752249ebcef
Gitweb:
https://git.kernel.org/tip/e927e62d8e370ebfc0d702fec22bc752249ebcef
Author:Joerg Roedel
AuthorDate:Fri, 12 Mar 2021 13:38:22 +01:00
Committer:
The following commit has been merged into the x86/seves branch of tip:
Commit-ID: 1ccdbf748d862bc2ea106fa9f2300983c77860fe
Gitweb:
https://git.kernel.org/tip/1ccdbf748d862bc2ea106fa9f2300983c77860fe
Author:Joerg Roedel
AuthorDate:Wed, 10 Mar 2021 09:43:22 +01:00
Committer:
The following commit has been merged into the x86/seves branch of tip:
Commit-ID: f15a0a732aefb46f999c2a8aa8f9f16e71cec5b2
Gitweb:
https://git.kernel.org/tip/f15a0a732aefb46f999c2a8aa8f9f16e71cec5b2
Author:Joerg Roedel
AuthorDate:Fri, 12 Mar 2021 13:38:24 +01:00
Committer:
The following commit has been merged into the x86/seves branch of tip:
Commit-ID: fef81c86262879d4b1176ef51a834c15b805ebb9
Gitweb:
https://git.kernel.org/tip/fef81c86262879d4b1176ef51a834c15b805ebb9
Author:Joerg Roedel
AuthorDate:Fri, 12 Mar 2021 13:38:23 +01:00
Committer:
On 3/18/21 4:58 PM, Suman Anna wrote:
> Hi All,
>
> The following series enhances the K3 R5F remoteproc driver to add support
> for the R5F clusters on the newer TI K3 AM64x SoC family. The AM64x SoCs
> have 2 R5FSS clusters and no DSPs. Both clusters are capable of supporting
> either the convent
The K3 AM64x SoC family has a revised R5F sub-system and contains a
subset of the R5F clusters present on J721E SoCs. The K3 AM64x SoCs
only have two dual-core Arm R5F clusters/subsystems with 2 R5F cores
each present within the MAIN voltage domain (MAIN_R5FSS0 & MAIN_R5FSS1).
The revised IP has t
The K3 AM64x SoCs have two dual-core Arm R5F clusters/subsystems, with
2 R5F cores each, both in the MAIN voltage domain.
These clusters are a revised IP version compared to those present on
J721E and J7200 SoCs, and supports a new "Single-CPU" mode instead of
LockStep mode. Update the K3 R5F remo
Hi All,
The following series enhances the K3 R5F remoteproc driver to add support
for the R5F clusters on the newer TI K3 AM64x SoC family. The AM64x SoCs
have 2 R5FSS clusters and no DSPs. Both clusters are capable of supporting
either the conventional Split-mode or a brand new "Single-CPU" mode.
301 - 400 of 1466 matches
Mail list logo
