Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

8273456: Do not hold ttyLock around stack walking #5445

Closed
wants to merge 1 commit into from

Conversation

coleenp
Copy link
Contributor

@coleenp coleenp commented Sep 9, 2021

This change moves the tty rank back down to near access, and prints stack traces to stringStream to avoid holding the tty lock while trying to take the stackwatermark lock.
Tested with tier1-8 (7,8 still in progress but no failures so far).


Progress

  • Change must not contain extraneous whitespace
  • Commit message must refer to an issue
  • Change must be properly reviewed

Issue

  • JDK-8273456: Do not hold ttyLock around stack walking

Reviewers

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/5445/head:pull/5445
$ git checkout pull/5445

Update a local copy of the PR:
$ git checkout pull/5445
$ git pull https://git.openjdk.java.net/jdk pull/5445/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 5445

View PR using the GUI difftool:
$ git pr show -t 5445

Using diff file

Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/5445.diff

@@ -210,7 +244,6 @@ static bool rematerialize_objects(JavaThread* thread, int exec_mode, CompiledMet
return_value = Handle(thread, result);
assert(Universe::heap()->is_in_or_null(result), "must be heap pointer");
if (TraceDeoptimization) {
ttyLocker ttyl;
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The change also removes obvious places where ttyLocker isn't needed.

@bridgekeeper
Copy link

bridgekeeper bot commented Sep 9, 2021

👋 Welcome back coleenp! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

@openjdk openjdk bot added the rfr Pull request is ready for review label Sep 9, 2021
@openjdk
Copy link

openjdk bot commented Sep 9, 2021

@coleenp The following label will be automatically applied to this pull request:

  • hotspot

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command.

@openjdk openjdk bot added the hotspot hotspot-dev@openjdk.org label Sep 9, 2021
@mlbridge
Copy link

mlbridge bot commented Sep 9, 2021

Webrevs

Copy link
Member

@dholmes-ora dholmes-ora left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi Coleen,

My only minor concern with these changes is that we lose information if there is a crash during any of these logging loops. Before you would (should?) see how far we got before a crash, but now there will not be any indication of that. But that is not the primary intention of this logging so I think the changes are okay.

Thanks,
David

@openjdk
Copy link

openjdk bot commented Sep 9, 2021

@coleenp This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

After integration, the commit message for the final commit will be:

8273456: Do not hold ttyLock around stack walking

Reviewed-by: dholmes, eosterlund

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been 18 new commits pushed to the master branch:

As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

@openjdk openjdk bot added the ready Pull request is ready to be integrated label Sep 9, 2021
@coleenp
Copy link
Contributor Author

coleenp commented Sep 10, 2021

I guess if you crashed you could look at st in the debugger. Thanks for the review!

Copy link
Contributor

@fisk fisk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good.

@coleenp
Copy link
Contributor Author

coleenp commented Sep 10, 2021

Thanks Erik!
/integrate

@openjdk
Copy link

openjdk bot commented Sep 10, 2021

Going to push as commit 461a467.
Since your change was applied there have been 18 commits pushed to the master branch:

Your commit was automatically rebased without conflicts.

@openjdk openjdk bot closed this Sep 10, 2021
@openjdk openjdk bot added integrated Pull request has been integrated and removed ready Pull request is ready to be integrated rfr Pull request is ready for review labels Sep 10, 2021
@openjdk
Copy link

openjdk bot commented Sep 10, 2021

@coleenp Pushed as commit 461a467.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.

@coleenp coleenp deleted the tty branch September 10, 2021 14:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hotspot hotspot-dev@openjdk.org integrated Pull request has been integrated
Development

Successfully merging this pull request may close these issues.

3 participants