From: osstest service owner <osstest-admin@xenproject.org>
To: xen-devel@lists.xenproject.org
Subject: [xen-unstable-smoke bisection] complete build-amd64
Date: Tue, 15 Mar 2022 02:25:52 +0000 [thread overview]
Message-ID: <E1nTwsi-0000FL-9b@osstest.test-lab.xenproject.org> (raw)
branch xen-unstable-smoke
xenbranch xen-unstable-smoke
job build-amd64
testid xen-build
Tree: qemu git://xenbits.xen.org/qemu-xen-traditional.git
Tree: qemuu git://xenbits.xen.org/qemu-xen.git
Tree: xen git://xenbits.xen.org/xen.git
*** Found and reproduced problem changeset ***
Bug is in tree: xen git://xenbits.xen.org/xen.git
Bug introduced: 9e5a68a6652cc54ce3cb3b0ce208eeed79d5aeb5
Bug not present: f9dd8436e3b826e4ca2284effa4c0285527ea763
Last fail repro: http://logs.test-lab.xenproject.org/osstest/logs/168603/
commit 9e5a68a6652cc54ce3cb3b0ce208eeed79d5aeb5
Author: Ayan Kumar Halder <ayan.kumar.halder@xilinx.com>
Date: Thu Mar 10 17:44:59 2022 +0000
xen/arm64: io: Support instructions (for which ISS is not valid) on emulated MMIO region using MMIO/ioreq handler
When an instruction is trapped in Xen due to translation fault, Xen
checks if the ISS is invalid (for data abort) or it is an instruction
abort. If so, Xen tries to resolve the translation fault using p2m page
tables. In case of data abort, Xen will try to map the mmio region to
the guest (ie tries to emulate the mmio region).
If the ISS is not valid and it is a data abort, then Xen tries to
decode the instruction. In case of ioreq, Xen saves the decoding state,
rn and imm9 to vcpu_io. Whenever the vcpu handles the ioreq successfully,
it will read the decoding state to determine if the instruction decoded
was a ldr/str post indexing (ie INSTR_LDR_STR_POSTINDEXING). If so, it
uses these details to post increment rn.
In case of mmio handler, if the mmio operation was successful, then Xen
retrives the decoding state, rn and imm9. For state ==
INSTR_LDR_STR_POSTINDEXING, Xen will update rn.
If there is an error encountered while decoding/executing the instruction,
Xen will forward the abort to the guest.
Also, the logic to infer the type of instruction has been moved from
try_handle_mmio() to try_decode_instruction() which is called before.
try_handle_mmio() is solely responsible for handling the mmio operation.
Signed-off-by: Ayan Kumar Halder <ayankuma@xilinx.com>
Acked-by: Julien Grall <jgrall@amazon.com>
Reviewed-by: Stefano Stabellini <sstabellini@kernel.org>
For bisection revision-tuple graph see:
http://logs.test-lab.xenproject.org/osstest/results/bisect/xen-unstable-smoke/build-amd64.xen-build.html
Revision IDs in each graph node refer, respectively, to the Trees above.
----------------------------------------
Running cs-bisection-step --graph-out=/home/logs/results/bisect/xen-unstable-smoke/build-amd64.xen-build --summary-out=tmp/168603.bisection-summary --basis-template=168580 --blessings=real,real-bisect,real-retry xen-unstable-smoke build-amd64 xen-build
Searching for failure / basis pass:
168591 fail [host=himrod1] / 168580 [host=himrod2] 168509 [host=himrod2] 168495 ok.
Failure / basis pass flights: 168591 / 168495
(tree with no url: minios)
(tree with no url: ovmf)
(tree with no url: seabios)
Tree: qemu git://xenbits.xen.org/qemu-xen-traditional.git
Tree: qemuu git://xenbits.xen.org/qemu-xen.git
Tree: xen git://xenbits.xen.org/xen.git
Latest 3d273dd05e51e5a1ffba3d98c7437ee84e8f8764 a68d6d311c2d1fd9d2fa9a0768ea2353e8a79b42 fef5531fd8f311b347970568d77e7bf4feffd7fb
Basis pass 3d273dd05e51e5a1ffba3d98c7437ee84e8f8764 a68d6d311c2d1fd9d2fa9a0768ea2353e8a79b42 5142dc5c25e317c208e3dc16d16b664b9f05dab5
Generating revisions with ./adhoc-revtuple-generator git://xenbits.xen.org/qemu-xen-traditional.git#3d273dd05e51e5a1ffba3d98c7437ee84e8f8764-3d273dd05e51e5a1ffba3d98c7437ee84e8f8764 git://xenbits.xen.org/qemu-xen.git#a68d6d311c2d1fd9d2fa9a0768ea2353e8a79b42-a68d6d311c2d1fd9d2fa9a0768ea2353e8a79b42 git://xenbits.xen.org/xen.git#5142dc5c25e317c208e3dc16d16b664b9f05dab5-fef5531fd8f311b347970568d77e7bf4feffd7fb
From git://cache:9419/git://xenbits.xen.org/xen
6ff9a7e62b..dedb0aa42c master -> origin/master
Loaded 5001 nodes in revision graph
Searching for test results:
168495 pass 3d273dd05e51e5a1ffba3d98c7437ee84e8f8764 a68d6d311c2d1fd9d2fa9a0768ea2353e8a79b42 5142dc5c25e317c208e3dc16d16b664b9f05dab5
168509 [host=himrod2]
168580 [host=himrod2]
168589 fail 3d273dd05e51e5a1ffba3d98c7437ee84e8f8764 a68d6d311c2d1fd9d2fa9a0768ea2353e8a79b42 fef5531fd8f311b347970568d77e7bf4feffd7fb
168590 pass 3d273dd05e51e5a1ffba3d98c7437ee84e8f8764 a68d6d311c2d1fd9d2fa9a0768ea2353e8a79b42 5142dc5c25e317c208e3dc16d16b664b9f05dab5
168593 fail 3d273dd05e51e5a1ffba3d98c7437ee84e8f8764 a68d6d311c2d1fd9d2fa9a0768ea2353e8a79b42 fef5531fd8f311b347970568d77e7bf4feffd7fb
168594 pass 3d273dd05e51e5a1ffba3d98c7437ee84e8f8764 a68d6d311c2d1fd9d2fa9a0768ea2353e8a79b42 3f809886988767fff46f440f4fc6d252fb586ace
168595 pass 3d273dd05e51e5a1ffba3d98c7437ee84e8f8764 a68d6d311c2d1fd9d2fa9a0768ea2353e8a79b42 dedb0aa42c6d1ee31805dfc61630db2c41117330
168596 pass 3d273dd05e51e5a1ffba3d98c7437ee84e8f8764 a68d6d311c2d1fd9d2fa9a0768ea2353e8a79b42 f9dd8436e3b826e4ca2284effa4c0285527ea763
168597 fail 3d273dd05e51e5a1ffba3d98c7437ee84e8f8764 a68d6d311c2d1fd9d2fa9a0768ea2353e8a79b42 9e5a68a6652cc54ce3cb3b0ce208eeed79d5aeb5
168598 pass 3d273dd05e51e5a1ffba3d98c7437ee84e8f8764 a68d6d311c2d1fd9d2fa9a0768ea2353e8a79b42 f9dd8436e3b826e4ca2284effa4c0285527ea763
168599 fail 3d273dd05e51e5a1ffba3d98c7437ee84e8f8764 a68d6d311c2d1fd9d2fa9a0768ea2353e8a79b42 9e5a68a6652cc54ce3cb3b0ce208eeed79d5aeb5
168600 pass 3d273dd05e51e5a1ffba3d98c7437ee84e8f8764 a68d6d311c2d1fd9d2fa9a0768ea2353e8a79b42 f9dd8436e3b826e4ca2284effa4c0285527ea763
168591 fail 3d273dd05e51e5a1ffba3d98c7437ee84e8f8764 a68d6d311c2d1fd9d2fa9a0768ea2353e8a79b42 fef5531fd8f311b347970568d77e7bf4feffd7fb
168603 fail 3d273dd05e51e5a1ffba3d98c7437ee84e8f8764 a68d6d311c2d1fd9d2fa9a0768ea2353e8a79b42 9e5a68a6652cc54ce3cb3b0ce208eeed79d5aeb5
Searching for interesting versions
Result found: flight 168495 (pass), for basis pass
For basis failure, parent search stopping at 3d273dd05e51e5a1ffba3d98c7437ee84e8f8764 a68d6d311c2d1fd9d2fa9a0768ea2353e8a79b42 f9dd8436e3b826e4ca2284effa4c0285527ea763, results HASH(0x55566074f348) HASH(0x55566074e8a0) HASH(0x555660756588) For basis failure, parent search stopping at 3d273dd05e51e5a1ffba3d98c7437ee84e8f8764 a68d6d311c2d1fd9d2fa9a0768ea2353e8a79b42 dedb0aa42c6d1ee31805dfc61630db2c41117330, results HASH(0x55566074d318) For basis failure, parent search stopping at 3d273dd05e51e5a1\
ffba3d98c7437ee84e8f8764 a68d6d311c2d1fd9d2fa9a0768ea2353e8a79b42 3f809886988767fff46f440f4fc6d252fb586ace, results HASH(0x55566074b310) For basis failure, parent search stopping at 3d273dd05e51e5a1ffba3d98c7437ee84e8f8764 a68d6d311c2d1fd9d2fa9a0768ea2353e8a79b42 5142dc5c25e317c208e3dc16d16b664b9f05dab5, results HASH(0x555660741920) HASH(0x555660748a08) Result found: flight 168589 (fail), for basis failure (at ancestor ~307)
Repro found: flight 168590 (pass), for basis pass
Repro found: flight 168591 (fail), for basis failure
0 revisions at 3d273dd05e51e5a1ffba3d98c7437ee84e8f8764 a68d6d311c2d1fd9d2fa9a0768ea2353e8a79b42 f9dd8436e3b826e4ca2284effa4c0285527ea763
No revisions left to test, checking graph state.
Result found: flight 168596 (pass), for last pass
Result found: flight 168597 (fail), for first failure
Repro found: flight 168598 (pass), for last pass
Repro found: flight 168599 (fail), for first failure
Repro found: flight 168600 (pass), for last pass
Repro found: flight 168603 (fail), for first failure
*** Found and reproduced problem changeset ***
Bug is in tree: xen git://xenbits.xen.org/xen.git
Bug introduced: 9e5a68a6652cc54ce3cb3b0ce208eeed79d5aeb5
Bug not present: f9dd8436e3b826e4ca2284effa4c0285527ea763
Last fail repro: http://logs.test-lab.xenproject.org/osstest/logs/168603/
commit 9e5a68a6652cc54ce3cb3b0ce208eeed79d5aeb5
Author: Ayan Kumar Halder <ayan.kumar.halder@xilinx.com>
Date: Thu Mar 10 17:44:59 2022 +0000
xen/arm64: io: Support instructions (for which ISS is not valid) on emulated MMIO region using MMIO/ioreq handler
When an instruction is trapped in Xen due to translation fault, Xen
checks if the ISS is invalid (for data abort) or it is an instruction
abort. If so, Xen tries to resolve the translation fault using p2m page
tables. In case of data abort, Xen will try to map the mmio region to
the guest (ie tries to emulate the mmio region).
If the ISS is not valid and it is a data abort, then Xen tries to
decode the instruction. In case of ioreq, Xen saves the decoding state,
rn and imm9 to vcpu_io. Whenever the vcpu handles the ioreq successfully,
it will read the decoding state to determine if the instruction decoded
was a ldr/str post indexing (ie INSTR_LDR_STR_POSTINDEXING). If so, it
uses these details to post increment rn.
In case of mmio handler, if the mmio operation was successful, then Xen
retrives the decoding state, rn and imm9. For state ==
INSTR_LDR_STR_POSTINDEXING, Xen will update rn.
If there is an error encountered while decoding/executing the instruction,
Xen will forward the abort to the guest.
Also, the logic to infer the type of instruction has been moved from
try_handle_mmio() to try_decode_instruction() which is called before.
try_handle_mmio() is solely responsible for handling the mmio operation.
Signed-off-by: Ayan Kumar Halder <ayankuma@xilinx.com>
Acked-by: Julien Grall <jgrall@amazon.com>
Reviewed-by: Stefano Stabellini <sstabellini@kernel.org>
Revision graph left in /home/logs/results/bisect/xen-unstable-smoke/build-amd64.xen-build.{dot,ps,png,html,svg}.
----------------------------------------
168603: tolerable ALL FAIL
flight 168603 xen-unstable-smoke real-bisect [real]
http://logs.test-lab.xenproject.org/osstest/logs/168603/
Failures :-/ but no regressions.
Tests which did not succeed,
including tests which could not be run:
build-amd64 6 xen-build fail baseline untested
jobs:
build-amd64 fail
------------------------------------------------------------
sg-report-flight on osstest.test-lab.xenproject.org
logs: /home/logs/logs
images: /home/logs/images
Logs, config files, etc. are available at
http://logs.test-lab.xenproject.org/osstest/logs
Explanation of these reports, and of osstest in general, is at
http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README.email;hb=master
http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README;hb=master
Test harness code can be found at
http://xenbits.xen.org/gitweb?p=osstest.git;a=summary
next reply other threads:[~2022-03-15 2:26 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-15 2:25 osstest service owner [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-28 17:02 [xen-unstable-smoke bisection] complete build-amd64 osstest service owner
2023-09-06 16:46 osstest service owner
2023-06-07 16:24 osstest service owner
2023-03-24 22:28 osstest service owner
2022-10-16 8:24 osstest service owner
2022-01-21 3:38 osstest service owner
2022-01-21 7:54 ` Jan Beulich
2021-08-16 23:23 osstest service owner
2021-07-10 0:19 osstest service owner
2021-07-06 17:29 osstest service owner
2021-02-24 16:57 osstest service owner
2021-02-10 19:10 osstest service owner
2021-01-28 18:38 osstest service owner
2020-12-21 20:07 osstest service owner
2020-11-10 23:25 osstest service owner
2020-10-23 23:30 osstest service owner
2020-10-07 18:40 osstest service owner
2020-04-25 8:57 osstest service owner
2019-05-15 8:13 osstest service owner
2019-04-13 5:09 osstest service owner
2019-04-13 15:51 ` Julien Grall
2019-04-13 15:53 ` Andrew Cooper
2019-01-02 21:14 osstest service owner
2018-11-12 23:38 osstest service owner
2018-09-25 21:39 osstest service owner
2018-04-07 6:19 osstest service owner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1nTwsi-0000FL-9b@osstest.test-lab.xenproject.org \
--to=osstest-admin@xenproject.org \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).