Page MenuHomeFreeBSD

sched_4bsd: remove dumping from maybe_preempt()
ClosedPublic

Authored by mchoo on Fri, Sep 4, 5:36 PM.
Tags
None
Referenced Files
Unknown Object (File)
Wed, Sep 30, 6:40 PM
Unknown Object (File)
Tue, Sep 29, 5:47 AM
Unknown Object (File)
Mon, Sep 28, 1:17 PM
Unknown Object (File)
Fri, Sep 25, 8:11 AM
Unknown Object (File)
Wed, Sep 23, 7:25 AM
Unknown Object (File)
Tue, Sep 22, 11:47 PM
Unknown Object (File)
Tue, Sep 22, 10:58 PM
Unknown Object (File)
Tue, Sep 22, 7:46 PM
Subscribers

Details

Summary

'dumping' is true only when kernel is dumping after crash (see
minidumpsys()) so KERNEL_PANICKED() will catch this.

MFC after: 2 weeks
MFC to: stable/14, stable/15
Sponsored by: FreeBSD Foundation

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Skipped
Unit
No Test Coverage
Build Status
Buildable 76609
Build 73492: arc lint + arc unit

Event Timeline

mchoo requested review of this revision.Fri, Sep 4, 5:36 PM
olce requested changes to this revision.Sun, Sep 6, 3:53 PM

Mmm, that's not true since we have been having live (mini)dump. On the contrary, it is perhaps time to put back dumping here and in ULE.

This revision now requires changes to proceed.Sun, Sep 6, 3:53 PM

Mmm, that's not true since we have been having live (mini)dump. On the contrary, it is perhaps time to put back dumping here and in ULE.

Makes sense, I'll open a new revision for that.

Actually, dumping is not set to true during live dump, so I think the patch is still correct.

int
minidumpsys(struct dumperinfo *di, bool livedump)
{
	struct minidumpstate state;
	struct msgbuf mb_copy;
	char *msg_ptr;
	int error;

	if (livedump) {
		KASSERT(!dumping, ("live dump invoked from incorrect context"));
This revision now requires changes to proceed.Sun, Sep 6, 8:39 PM

Remove duplicated commit message template

On second thought, there is a balance between getting a consistent dump image and temporary disruption of the live system for live dumps. It's already the case that they do not guarantee a fully consistent image. And they don't try to stop CPUs, the scheduler, etc. As you point out, minidump is not set, which in this line of thinking is not surprising.

So let's proceed with that.

This revision is now accepted and ready to land.Sun, Sep 6, 9:18 PM