Linus,
please pull the latest objtool/core branch from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
objtool-core-2021-02-23
up to: aafeb14e9da2: objtool: Support stack-swizzle
objtool updates:
- Make objtool work for big-endian cross compiles
- Make stack tracking via
| 2 +-
> arch/mips/sgi-ip32/ip32-irq.c | 2 +-
> 3 files changed, 3 insertions(+), 3 deletions(-)
applied only this patch to mips-next.
For the other patches I'll wait for how the resolution for linux-mips.org
looks like.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but
a.$L* to grab these ones into .data too.
>
> [0] https://lore.kernel.org/lkml/202102231519.lwplpvev-...@intel.com
>
> Reported-by: kernel test robot
> Signed-off-by: Alexander Lobakin
> ---
> include/asm-generic/vmlinux.lds.h | 2 +-
> 1 file changed, 1 insertion(+), 1 delet
`init/calibrate.o' being placed in section `.data.$LPBX0'
> >
> > [...]
> >
> > Soften the wildcard to .data.$L* to grab these ones into .data too.
> >
> > [0] https://lore.kernel.org/lkml/202102231519.lwplpvev-...@intel.com
> >
> > Reported-by: kernel test rob
changed, 1 insertion(+), 1 deletion(-)
applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.[ RFC1925, 2.3 ]
On Mon, Feb 22 2021 at 21:50, Andy Lutomirski wrote:
> On a 32-bit fast syscall that fails to read its arguments from user
> memory, the kernel currently does syscall exit work but not
> syscall exit work.
and this sentence does not make any sense.
> This would confuse audit and ptrace.
Would?
Linus,
please pull the latest timers/urgent branch from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
timers-urgent-2021-02-22
up to: 8acb54abc1db: Merge tag 'timers-v5.11-rc5' of
https://git.linaro.org/people/daniel.lezcano/linux into timers/urgent
A small set of clockevent
The following commit has been merged into the timers/urgent branch of tip:
Commit-ID: 8acb54abc1db4e1e3913359e4108e04e88ce4d92
Gitweb:
https://git.kernel.org/tip/8acb54abc1db4e1e3913359e4108e04e88ce4d92
Author:Thomas Gleixner
AuthorDate:Mon, 22 Feb 2021 10:59:13 +01:00
Daniel,
On Mon, Feb 22 2021 at 09:36, Daniel Lezcano wrote:
> those fixes were not picked up
Ooops. Taking care right now.
]---
[ 153.838441] [drm:drm_mode_config_cleanup] *ERROR* connector VGA-1 leaked!
Signed-off-by: Tong Zhang
I've added the patch to drm-misc-next. Thanks a lot!
Best regards
Thomas
---
drivers/gpu/drm/ast/ast_drv.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/gpu/drm/ast
viewed-by: Ville Syrjälä
Signed-off-by: Maxime Ripard
Acked-by: Thomas Zimmermann
However, I find 'old plane state' somewhat confusing in this context,
because it's actually the current plane state. Would it make sense to
use drm_atomic_get_existing_plane_state() instead?
Best regard
te *state) {
...
struct drm_plane_state *plane_state = drm_atomic_get_new_plane_state(state,
plane);
<...
- plane_state->state
+ state
...>
}
Reviewed-by: Laurent Pinchart
Signed-off-by: Maxime Ripard
Acked-by: Thomas Zimmermann
---
Changes from v1:
- Fixed the formatt
Am 19.02.21 um 16:12 schrieb Maxime Ripard:
Hi Thomas,
Thanks for your review!
On Fri, Feb 19, 2021 at 03:49:22PM +0100, Thomas Zimmermann wrote:
diff --git a/drivers/gpu/drm/imx/ipuv3-plane.c
b/drivers/gpu/drm/imx/ipuv3-plane.c
index 075508051b5f..1873a155bb26 100644
--- a/drivers/gpu/drm
{ ... }
@ include depends on adds_new_state @
@@
#include
@ no_include depends on !include && adds_new_state @
@@
+ #include
#include
Reviewed-by: Laurent Pinchart
Signed-off-by: Maxime Ripard
Acked-by: Thomas Zimmermann
---
Changes from v1:
- Rewording and removal of
...
Thanks for your patch. I've added it to drm-misc-next.
Best regards
Thomas
---
drivers/video/fbdev/efifb.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/video/fbdev/efifb.c b/drivers/video/fbdev/efifb.c
index e57c00824965..19edd7206409 100644
--- a/drivers/video/fbdev
Am 19.02.21 um 13:00 schrieb Maxime Ripard:
Most drivers call the argument to the plane atomic_check hook simply
state, which is going to conflict with the global atomic state in a
later rework. Let's rename it to new_plane_state (or new_state depending
on the convention used in the driver).
*
#define SDATA_MAIN .sdata .sdata.[0-9a-zA-Z_]*
#define RODATA_MAIN .rodata .rodata.[0-9a-zA-Z_]* .rodata..L*
#define BSS_MAIN .bss .bss.[0-9a-zA-Z_]* .bss..compoundliteral*
Thomas.
The following changes since commit 5c8fe583cce542aa0b84adc939ce85293de36e5e:
Linux 5.11-rc1 (2020-12-27 15
Hi
Am 18.02.21 um 16:07 schrieb Christoph Hellwig:
On Thu, Feb 18, 2021 at 03:56:00PM +0100, Thomas Zimmermann wrote:
I only have udl devices, but I expect that other DRM USB adapters are also
affected.
Find where the driver calls dma_map_* itself instead of using the USB
wrappers and fix
* error in the dmesg log
I only have udl devices, but I expect that other DRM USB adapters are
also affected.
How to fix this?
Best regards
Thomas
[ 60.050199] [ cut here ]
[ 60.055092] WARNING: CPU: 0 PID: 1403 at kernel/dma/mapping.c:190
dma_map_sg_attrs+0x8f/0xc0
[
Am 17.02.21 um 13:32 schrieb Gerd Hoffmann:
Use the correct vmap variant. We don't hold a reservation here,
so we can't use the _locked variant. We can drop the pin because
qxl_bo_vmap will do that for us.
Signed-off-by: Gerd Hoffmann
Acked-by: Thomas Zimmermann
I simply forgot to ack
-by: Thomas Zimmermann
for patches 9 and 10. Having the vmap calls fixed is at least worth it.
Best regards
Thomas
So, no, I have no short-term plans for qxl beyond fixing pins +
reservations + lockdep.
take care,
Gerd
___
dri-devel mailing list
dri
On Tue, Feb 16, 2021 at 02:55:36PM +0100, Maciej W. Rozycki wrote:
> On Fri, 12 Feb 2021, Thomas Bogendoerfer wrote:
>
> > > IMHO ptrace single step is for CPUs supporting single stepping and not
> > > for emulating it in the kernel.
> >
> > I've checked other
handling?
For now, I suggest to merge patch 1 to 8 and 11; and move the cursor
patches into a new patchset. I'd like ot hear Daniel's opinion on this.
Do you have further plans here?
If you absolutely want patches 9 and 10, I'd rubber-stamp an A-b on them.
Best regards
Thomas
Signed-off-by: Gerd
Am 17.02.21 um 13:32 schrieb Gerd Hoffmann:
Append _locked to Make clear that these functions should be called with
reserved bo's only. While being at it also rename kmap -> vmap.
No functional change.
Signed-off-by: Gerd Hoffmann
Acked-by: Thomas Zimmermann
---
drivers/gpu/drm/
Am 17.02.21 um 13:32 schrieb Gerd Hoffmann:
Add vmap/vunmap variants which reserve (and pin) the bo.
They can be used in case the caller doesn't hold a reservation
for the bo.
Signed-off-by: Gerd Hoffmann
Acked-by: Thomas Zimmermann
---
drivers/gpu/drm/qxl/qxl_object.h | 2
Am 17.02.21 um 13:32 schrieb Gerd Hoffmann:
Call qxl_bo_unpin (which does a reservation) without holding the
release_mutex lock. Fixes lockdep (correctly) warning on a possible
deadlock.
Fixes: 65ffea3c6e73 ("drm/qxl: unpin release objects")
Signed-off-by: Gerd Hoffmann
Acked-
it *much* less likely that
ttm_bo_mem_force_space() picks something which can't be evicted and
throws an error after waiting a while without success.
Signed-off-by: Gerd Hoffmann
Acked-by: Thomas Zimmermann
---
drivers/gpu/drm/qxl/qxl_object.h | 1 +
drivers/gpu/drm/qxl/qxl_cmd.c | 2
_wait")
Signed-off-by: Gerd Hoffmann
Acked-by: Thomas Zimmermann
---
drivers/gpu/drm/qxl/qxl_release.c | 8 ++--
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/drivers/gpu/drm/qxl/qxl_release.c
b/drivers/gpu/drm/qxl/qxl_release.c
index 6ed673d75f9f..579c6de10
.
There are no users of drm_get_format_name() in linux-next
currently after the 3rd patch.
I've merged patches 1 to 3 into drm-misc-next. Patch 4 (and maybe some
final fix-up patch) will land when all DRM trees have catched up the
changes.
Best regards
Thomas
This set adds support for %p4cc printk
Hi
Am 17.02.21 um 11:02 schrieb Gerd Hoffmann:
On Tue, Feb 16, 2021 at 02:46:21PM +0100, Thomas Zimmermann wrote:
Am 16.02.21 um 14:27 schrieb Thomas Zimmermann:
Hi
this is a shadow-buffered plane. Did you consider using the new helpers
for shadow-buffered planes? They will map the user BO
UBSAN's "unnamed data" into data")
> Reported-by: kernel test robot
> Signed-off-by: Alexander Lobakin
> ---
> include/asm-generic/vmlinux.lds.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
applied to
Am 16.02.21 um 14:27 schrieb Thomas Zimmermann:
Hi
this is a shadow-buffered plane. Did you consider using the new helpers
for shadow-buffered planes? They will map the user BO for you and
provide the mapping in the plane state.
From there, you should implement your own plane state
Hi
Am 16.02.21 um 12:37 schrieb Gerd Hoffmann:
Try avoid re-introducing locking bugs.
Signed-off-by: Gerd Hoffmann
Acked-by: Thomas Zimmermann
IMHO this should eventually be done in the rsp TTM functions. But so
far, I'd expect this to break some drivers.
Best regards
Thomas
all the other allocations and
vmaps into prepare_fb and cleanup_fb. Most of this is not actually
allowed in commit tails. All we'd have to do is to export the reset,
duplicate and destroy code; similar to what
__drm_atomic_helper_plane_reset() does.
Best regards
Thomas
Am 16.02.21 um 12:37
Am 16.02.21 um 12:37 schrieb Gerd Hoffmann:
Use the correct kmap variant. We don't hold a reservation here,
so we can't use the _locked variant. We can drop the pin because
qxl_bo_kmap will do that for us.
Signed-off-by: Gerd Hoffmann
Acked-by: Thomas Zimmermann
---
drivers/gpu/drm
erve(bo);
+ return 0;
+}
+
void qxl_bo_kunmap_atomic_page(struct qxl_device *qdev,
struct qxl_bo *bo, void *pmap)
{
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5, 90409 Nürnberg, Germany
(HRB 36809, AG
Hi
Am 16.02.21 um 12:37 schrieb Gerd Hoffmann:
Use the correct kmap variant. We don't have a reservation here,
so we can't use the _locked version.
I'd merge this change into patch 6. So the new functions come with a caller.
Best regards
Thomas
Signed-off-by: Gerd Hoffmann
---
drivers
/kunmap is a misnomer. Since you're renaming; maybe
rename them to vmap/vunmap.
Best regards
Thomas
void *qxl_bo_kmap_atomic_page(struct qxl_device *qdev, struct qxl_bo *bo, int
page_offset);
void qxl_bo_kunmap_atomic_page(struct qxl_device *qdev, struct qxl_bo *bo,
void *map);
extern
Am 16.02.21 um 12:37 schrieb Gerd Hoffmann:
Specifically do not try release resources which where
not allocated in the first place.
I still think this should eventually be resolved by using managed code.
But for now
Acked-by: Thomas Zimmermann
Cc: Tong Zhang
Tested-by: Tong Zhang
The following commit has been merged into the x86/entry branch of tip:
Commit-ID: 3aac798a917be3b8f2f647b834bb06bf2f8df4f1
Gitweb:
https://git.kernel.org/tip/3aac798a917be3b8f2f647b834bb06bf2f8df4f1
Author:Thomas Gleixner
AuthorDate:Tue, 16 Feb 2021 10:23:14 +01:00
d179b0e66 ("z3fold: stricter locking and more careful reclaim")
Signed-off-by: Thomas Hebb
---
I have NOT tested this patch yet beyond compiling it. If the approach
seems good, I'll test it on my system for a period of several days and
see if I can reproduce the crash before sending a v
/drm/drm_fourcc.h | 1 -
27 files changed, 64 insertions(+), 157 deletions(-)
This is a nice patchset. For the driver-related changes:
Acked-by: Thomas Zimmermann
But landing this patch will certainly give us build errors. There are at
least 3 git trees involved: drm-misc
Linus,
please pull the latest timers/core branch from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
timers-core-2021-02-15
up to: 11db5710d4a9: Merge tag 'timers-v5.12-rc1' of
https://git.linaro.org/people/daniel.lezcano/linux into timers/core
Time and timer updates:
-
Linus,
please pull the latest irq/core branch from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git irq-core-2021-02-15
up to: 0b6d70e571a1: Merge tag 'irqchip-5.12' of
git://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms into irq/core
Updates for the irq subsystem:
se the parent of
the aux device, since that technically doesn't need to be the drm driver).
I'd add it in this series, but that's going to involve updating functions across
the tree like drm_dp_aux_init() so I'd like to do it in a different patch series
Ok, sure. Makes sense.
Best r
The following commit has been merged into the irq/core branch of tip:
Commit-ID: 0b6d70e571a1c764ab079e5c31d4156feee4b06b
Gitweb:
https://git.kernel.org/tip/0b6d70e571a1c764ab079e5c31d4156feee4b06b
Author:Thomas Gleixner
AuthorDate:Mon, 15 Feb 2021 15:41:56 +01:00
On Sat, Feb 13, 2021 at 03:02:31PM +0100, Thomas Bogendoerfer wrote:
> With the removal of set_fs() calls kgdb_call_nmi_hook() is now the same as
> the default implementation, so we can remove it.
>
> Signed-off-by: Thomas Bogendoerfer
> ---
> arch/mips/kernel/kgdb.c | 5 -
Hi
Am 15.02.21 um 10:49 schrieb Thomas Zimmermann:
Hi
Am 15.02.21 um 09:58 schrieb Christian König:
Hi guys,
we are currently working an Freesync and direct scan out from system
memory on AMD APUs in A+A laptops.
On problem we stumbled over is that our display hardware needs to scan
out
the
dma_buf is pinned.
Best regards
Thomas
After all the system memory access pattern is a PCIe extension and as
such something generic.
Regards,
Christian.
___
dri-devel mailing list
dri-de...@lists.freedesktop.org
https://lists.freedesktop.org
with transactional programming in userspace system
code. So FWIW
Acked-by: Thomas Zimmermann
Note that some distributions such as Ubuntu are already enabling
CHECKPOINT_RESTORE in their configs and so, by extension, SYS_kcmp.
References: https://gitlab.freedesktop.org/drm/intel/-/issues/3046
Signed-off
With the removal of set_fs() calls kgdb_call_nmi_hook() is now the same as
the default implementation, so we can remove it.
Signed-off-by: Thomas Bogendoerfer
---
arch/mips/kernel/kgdb.c | 5 -
1 file changed, 5 deletions(-)
diff --git a/arch/mips/kernel/kgdb.c b/arch/mips/kernel/kgdb.c
to fix uninitialized build warning used with clang
> reported by kernel test robot.
>
> arch/mips/include/asm/ptrace.h | 2 +
> arch/mips/include/asm/thread_info.h | 5 ++
> arch/mips/kernel/ptrace.c | 108
> +
On Wed, Feb 10, 2021 at 05:16:13PM +0100, Thomas Bogendoerfer wrote:
> This reverts commit 6ebda44f366478d1eea180d93154e7d97b591f50.
>
> All icache flushes in this code paths are done via flush_icache_range(),
> which only uses normal cache instruction. And this is the correct thi
On Wed, Feb 10, 2021 at 10:56:35AM +0100, Christoph Hellwig wrote:
> Hi Thomas,
>
> this series cleans up some of the mips (maybe) noncoherent support.
> It also remove the need for the special header only
> provided by mips.
>
> Changes since v1:
> - fix a bisectio
On Wed, Feb 10, 2021 at 05:16:14PM +0100, Thomas Bogendoerfer wrote:
> protected_cache_op is only used for flushing user addresses, so
> we only need to define protected_cache_op different in EVA mode and
> be done with it.
>
> Signed-off-by: Thomas Bogendoerfer
> ---
>
On Thu, Feb 11, 2021 at 11:29:05AM +0100, Thomas Bogendoerfer wrote:
> IMHO ptrace single step is for CPUs supporting single stepping and not
> for emulating it in the kernel.
I've checked other arch how they implement single step, and looks like
I'm wrong. So I'm ok with applying your patc
On Thu, Feb 11, 2021 at 01:59:35PM +0100, Paolo Bonzini wrote:
> On 10/02/21 17:19, Thomas Bogendoerfer wrote:
> > > arch/arm64/include/asm/spinlock.h | 2 +-
> > > arch/mips/include/asm/spinlock.h | 2 +-
> > > arch/xtensa/include/asm/spinlock.h | 2 +-
> &g
to match those patterns, just name the one file that matches
> explicitly and delete the others without a match.
>
> Signed-off-by: Lukas Bulwahn
> ---
> applies cleanly on current master and next-20210209
>
> Keguang, Huacai, Jiaxun, please ack.
>
> Thomas, please pi
SEND due to send to mail list failed.
>
> v3: update the commit message and modify the patch subject
>
> v2: add MIPS_DEBUG_DBP definition
>
> arch/mips/include/asm/mipsregs.h | 4
> arch/mips/kernel/genex.S | 4 ++--
> 2 files changed, 6 insertions(+), 2 d
Signed-off-by: Kees Cook
> ---
> This patch may make more sense if this entire comment and the related
> code is fixed instead (gcc 3.x has been quite retired...)
> ---
> arch/mips/include/asm/page.h | 11 +--
> 1 file changed, 5 insertions(+), 6 deletions(-)
applied to mi
that the Go debugger needs to learn
single stepping without ptrace single step support. IMHO gdb is already
able to do that.
IMHO ptrace single step is for CPUs supporting single stepping and not
for emulating it in the kernel.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's
The following commit has been merged into the x86/entry branch of tip:
Commit-ID: 359f01d1816fc1ea0161e6c30722bef1ed6b8abb
Gitweb:
https://git.kernel.org/tip/359f01d1816fc1ea0161e6c30722bef1ed6b8abb
Author:Thomas Gleixner
AuthorDate:Wed, 10 Feb 2021 00:40:49 +01:00
The following commit has been merged into the x86/entry branch of tip:
Commit-ID: 15f720aabe71a5662c4198b22532d95bbeec80ef
Gitweb:
https://git.kernel.org/tip/15f720aabe71a5662c4198b22532d95bbeec80ef
Author:Thomas Gleixner
AuthorDate:Wed, 10 Feb 2021 00:40:42 +01:00
The following commit has been merged into the x86/entry branch of tip:
Commit-ID: 5b51e1db9bdc312d53087a0c97d54ea150111c0d
Gitweb:
https://git.kernel.org/tip/5b51e1db9bdc312d53087a0c97d54ea150111c0d
Author:Thomas Gleixner
AuthorDate:Wed, 10 Feb 2021 00:40:48 +01:00
The following commit has been merged into the x86/entry branch of tip:
Commit-ID: e7f89001797148e8dc7060c335df2c56e73a8c7a
Gitweb:
https://git.kernel.org/tip/e7f89001797148e8dc7060c335df2c56e73a8c7a
Author:Thomas Gleixner
AuthorDate:Wed, 10 Feb 2021 00:40:43 +01:00
The following commit has been merged into the x86/entry branch of tip:
Commit-ID: 52d743f3b71265e14560a38f4c835d07b9c6fc4c
Gitweb:
https://git.kernel.org/tip/52d743f3b71265e14560a38f4c835d07b9c6fc4c
Author:Thomas Gleixner
AuthorDate:Wed, 10 Feb 2021 00:40:50 +01:00
The following commit has been merged into the x86/entry branch of tip:
Commit-ID: 951c2a51ae75382d519839e2308394ad43ce4b40
Gitweb:
https://git.kernel.org/tip/951c2a51ae75382d519839e2308394ad43ce4b40
Author:Thomas Gleixner
AuthorDate:Wed, 10 Feb 2021 00:40:44 +01:00
The following commit has been merged into the x86/entry branch of tip:
Commit-ID: a0cfc74d0b00c5201e1c09e28b2dc01c8088f809
Gitweb:
https://git.kernel.org/tip/a0cfc74d0b00c5201e1c09e28b2dc01c8088f809
Author:Thomas Gleixner
AuthorDate:Wed, 10 Feb 2021 00:40:46 +01:00
The following commit has been merged into the x86/entry branch of tip:
Commit-ID: 3c5e0267ec3e6ed7d3f1793273cbf0beb4f86a74
Gitweb:
https://git.kernel.org/tip/3c5e0267ec3e6ed7d3f1793273cbf0beb4f86a74
Author:Thomas Gleixner
AuthorDate:Wed, 10 Feb 2021 00:40:45 +01:00
The following commit has been merged into the x86/entry branch of tip:
Commit-ID: 569dd8b4eb7ef666b467c41b8e8e4f2820d07f67
Gitweb:
https://git.kernel.org/tip/569dd8b4eb7ef666b467c41b8e8e4f2820d07f67
Author:Thomas Gleixner
AuthorDate:Wed, 10 Feb 2021 00:40:47 +01:00
The following commit has been merged into the x86/entry branch of tip:
Commit-ID: 72f40a2823d6e16229ab58b898c6f22044e5222f
Gitweb:
https://git.kernel.org/tip/72f40a2823d6e16229ab58b898c6f22044e5222f
Author:Thomas Gleixner
AuthorDate:Wed, 10 Feb 2021 00:40:54 +01:00
The following commit has been merged into the x86/entry branch of tip:
Commit-ID: 624db9eabc74597f682c0651047a25b54f7260a1
Gitweb:
https://git.kernel.org/tip/624db9eabc74597f682c0651047a25b54f7260a1
Author:Thomas Gleixner
AuthorDate:Wed, 10 Feb 2021 00:40:51 +01:00
The following commit has been merged into the x86/entry branch of tip:
Commit-ID: db1cc7aede37eb9235759131ddfefd9c0ea5136f
Gitweb:
https://git.kernel.org/tip/db1cc7aede37eb9235759131ddfefd9c0ea5136f
Author:Thomas Gleixner
AuthorDate:Wed, 10 Feb 2021 00:40:53 +01:00
The following commit has been merged into the x86/entry branch of tip:
Commit-ID: cd1a41ceba8a4caef4d18a3a14d6d0f8c656efe4
Gitweb:
https://git.kernel.org/tip/cd1a41ceba8a4caef4d18a3a14d6d0f8c656efe4
Author:Thomas Gleixner
AuthorDate:Wed, 10 Feb 2021 00:40:52 +01:00
On Wed, Feb 10, 2021 at 07:11:00PM +, Christoph Hellwig wrote:
> On Wed, Feb 10, 2021 at 05:16:13PM +0100, Thomas Bogendoerfer wrote:
> > This reverts commit 6ebda44f366478d1eea180d93154e7d97b591f50.
> >
> > All icache flushes in this code paths are done via flush_icac
The following commit has been merged into the x86/urgent branch of tip:
Commit-ID: 70245f86c109e0eafb92ea9653184c0e44b4b35c
Gitweb:
https://git.kernel.org/tip/70245f86c109e0eafb92ea9653184c0e44b4b35c
Author:Thomas Gleixner
AuthorDate:Wed, 10 Feb 2021 16:27:41 +01:00
> arch/mips/include/asm/spinlock.h | 2 +-
> arch/xtensa/include/asm/spinlock.h | 2 +-
> 3 files changed, 3 insertions(+), 3 deletions(-)
which tree should this go through ? I can take it via mips-next,
if everybody agrees.
Thomas.
--
Crap can work. Given enough thrust pigs w
protected_cache_op is only used for flushing user addresses, so
we only need to define protected_cache_op different in EVA mode and
be done with it.
Signed-off-by: Thomas Bogendoerfer
---
arch/mips/include/asm/r4kcache.h | 67 ++--
1 file changed, 11 insertions
This reverts commit 6ebda44f366478d1eea180d93154e7d97b591f50.
All icache flushes in this code paths are done via flush_icache_range(),
which only uses normal cache instruction. And this is the correct thing
for EVA mode, too. So no need to do set_fs(KERNEL_DS) here.
Signed-off-by: Thomas
which runs out of vectors and causes malfunction.
Invoke it after x86_init.pci.arch_init().
Fixes: 6b15ffa07dc3 ("x86/irq: Initialize PCI/MSI domain at PCI init time")
Reported-by: Juergen Gross
Signed-off-by: Thomas Gleixner
Tested-by: Juergen Gross
Cc: sta...@vger.kernel.org
---
ar
On Wed, Feb 10 2021 at 19:39, Hikaru Nishida wrote:
> From: Hikaru Nishida
>
> This introduces timekeeping_adjust_boottime() to give an interface to
> modules that enables to advance CLOCK_BOOTTIME from userspace for
> virtualized environments. Later patch introduces a sysfs interface
> which
On Wed, Feb 10 2021 at 19:39, Hikaru Nishida wrote:
> From: Hikaru Nishida
>
> This adds a sysfs interface /sys/kernel/boottime_adj to enable advancing
> CLOCK_BOOTTIME from the userspace without actual susupend/resume cycles.
>
> This gives a way to mitigate CLOCK_BOOTTIME divergence between
On Wed, Feb 10, 2021 at 10:56:35AM +0100, Christoph Hellwig wrote:
> Hi Thomas,
>
> this series cleans up some of the mips (maybe) noncoherent support.
> It also remove the need for the special header only
> provided by mips.
>
> Changes since v1:
> - fix a bisectio
The following commit has been merged into the timers/core branch of tip:
Commit-ID: 11db5710d4a954148e00e376f04ba91a498a20dd
Gitweb:
https://git.kernel.org/tip/11db5710d4a954148e00e376f04ba91a498a20dd
Author:Thomas Gleixner
AuthorDate:Wed, 10 Feb 2021 11:02:20 +01:00
From: Thomas Gleixner
There is no reason to have this as a seperate function for a single caller.
Signed-off-by: Thomas Gleixner
Reviewed-by: Kees Cook
---
V2: Adopt to the new header file.
---
arch/x86/include/asm/irq_stack.h |3 +--
arch/x86/include/asm/softirq_stack.h | 11
of #ifdeffery all over the
place.
Signed-off-by: Thomas Gleixner
Cc: Lai Jiangshan
---
V2: New patch to get rid of the nested #ifdeffery - Lai
---
arch/parisc/kernel/irq.c|1 +
arch/powerpc/kernel/irq.c |1 +
arch/s390/kernel/irq.c |1 +
arch/sh/kernel/irq.c
From: Thomas Gleixner
To avoid yet another macro implementation reuse the existing
run_sysvec_on_irqstack_cond() and move the set_irq_regs() handling into the
called function. Makes the code even simpler.
Signed-off-by: Thomas Gleixner
Reviewed-by: Kees Cook
---
arch/x86/entry/common.c
include recursion.
Signed-off-by: Thomas Gleixner
Cc: Lai Jiangshan
---
V2: New patch to get rid of the nested #ifdeffery - Lai
---
arch/Kconfig |6 ++
arch/parisc/Kconfig |1 +
arch/parisc/include/asm/hardirq.h |4
arch/powerpc/Kconfig
From: Thomas Gleixner
To inline the stack switching and to prepare for enabling
CONFIG_HAVE_IRQ_EXIT_ON_IRQ_STACK provide a macro template for system
vectors and device interrupts and convert the system vectors over to it.
Signed-off-by: Thomas Gleixner
Reviewed-by: Kees Cook
---
V2: Adopt
From: Thomas Gleixner
sysvec_spurious_apic_interrupt() calls into the handling body of
__spurious_interrupt() which is not obvious as that function is declared
inside the DEFINE_IDTENTRY_IRQ(spurious_interrupt) macro.
As __spurious_interrupt() is currently always inlined this ends up with two
From: Thomas Gleixner
Now that all invocations of irq_exit_rcu() happen on the irq stack, turn on
CONFIG_HAVE_IRQ_EXIT_ON_IRQ_STACK which causes the core code to invoke
__do_softirq() directly without going through do_softirq_own_stack().
That means do_softirq_own_stack() is only invoked from
From: Thomas Gleixner
Embracing a callout into instrumentation_begin() / instrumentation_begin()
does not really make sense. Make the latter instrumentation_end().
Fixes: 2f6474e4636b ("x86/entry: Switch XEN/PV hypercall entry to IDTENTRY")
Signed-off-by: Thomas Gleixner
Reviewed-by:
This is the second version of this series. V1 is available here:
https://lore.kernel.org/r/20210204204903.350275...@linutronix.de
The recent effort to make the ASM entry code slim and unified moved
the irq stack switching out of the low level ASM code so that the
whole return from interrupt
From: Thomas Gleixner
Convert device interrupts to inline stack switching by replacing the
existing macro implementation with the new inline version. Tweak the
function signature of the actual handler function to have the vector
argument as u32. That allows the inline macro to avoid extra
From: Thomas Gleixner
Use the new inline stack switching and remove the old ASM indirect call
implementation.
Signed-off-by: Thomas Gleixner
Reviewed-by: Kees Cook
---
arch/x86/entry/entry_64.S| 39 -
arch/x86/include/asm/irq_stack.h | 52
From: Thomas Gleixner
The effort to make the ASM entry code slim and unified moved the irq stack
switching out of the low level ASM code so that the whole return from
interrupt work and state handling can be done in C and the ASM code just
handles the low level details of entry and exit
From: Thomas Gleixner
The per CPU hardirq_stack_ptr contains the pointer to the irq stack in the
form that it is ready to be assigned to [ER]SP so that the first push ends
up on the top entry of the stack.
But the stack switching on 64 bit has the following rules:
1) Store the current
From: Thomas Gleixner
The recursion protection for hard interrupt stacks is an unsigned int per
CPU variable initialized to -1 named __irq_count.
The irq stack switching is only done when the variable is -1, which creates
worse code than just checking for 0. When the stack switching happens
Lai,
On Fri, Feb 05 2021 at 12:38, Thomas Gleixner wrote:
> On Fri, Feb 05 2021 at 18:14, Lai Jiangshan wrote:
>> On Fri, Feb 5, 2021 at 10:04 AM Thomas Gleixner wrote:
>>> static inline void do_softirq_own_stack(void)
>>> {
>>
>> Hello
>>
>>
On Tue, Feb 09 2021 at 10:22, Josh Poimboeuf wrote:
> On Tue, Feb 09, 2021 at 04:12:33PM +0100, Thomas Gleixner wrote:
>> On Mon, Feb 08 2021 at 14:42, Josh Poimboeuf wrote:
>> > On Thu, Feb 04, 2021 at 09:49:08PM +0100, Thomas Gleixner wrote:
>> >> #ifdef CONFI
601 - 700 of 38837 matches
Mail list logo
