On 02/02/2015 14:50, Pavel Dovgaluk wrote:
> I think not. We just have to write number of already executed instructions.
> This number is not linked to exception event. They could be read in replay
> while
> processing some other event.
>
I was referring to replay_put_event(EVENT_EXCEPTION) o
> From: Paolo Bonzini [mailto:pbonz...@redhat.com]
> On 22/01/2015 09:52, Pavel Dovgalyuk wrote:
> > +if (replay_mode == REPLAY_MODE_RECORD) {
> > +replay_save_instructions();
> > +replay_put_event(EVENT_EXCEPTION);
> > +return true;
>
> Missing mutex lock/unlock.
I th
On 22/01/2015 09:52, Pavel Dovgalyuk wrote:
> +if (replay_mode == REPLAY_MODE_RECORD) {
> +replay_save_instructions();
> +replay_put_event(EVENT_EXCEPTION);
> +return true;
Missing mutex lock/unlock.
> +} else if (replay_mode == REPLAY_MODE_PLAY) {
> +boo
This patch includes modifications of common cpu files. All interrupts and
exceptions occured during recording are written into the replay log.
These events allow correct replaying the execution by kicking cpu thread
when one of these events is found in the log.
Signed-off-by: Pavel Dovgalyuk
---
