public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: nitin.a.kamble-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org
Cc: kvm-devel
	<kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
	"Yu,
	 Wilfred" <wilfred.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: [Patch] (big) real mode emulation - push reg
Date: Fri, 17 Aug 2007 15:21:10 +0300	[thread overview]
Message-ID: <46C592B6.8030700@qumranet.com> (raw)
In-Reply-To: <1187307993.10269.8.camel-mpPvwfgnXtFHIUuj5cj4Omt3HXsI98Cx0E9HWUfgJXw@public.gmane.org>

Nitin A Kamble wrote:
> Hi Avi,
>  Attached is a patch to implement instruction:
> 	push reg (opcode 0x50 - 0x57)
> Please apply or comment.
> 	
>   
> +	case 0x50 ... 0x57:  /* push reg */
> +		if (op_bytes == 2)
> +			src.val = (u16) _regs[b & 0x7];
> +		else
> +			src.val = (u32) _regs[b & 0x7];
> +		dst.type  = OP_MEM;
> +		dst.bytes = op_bytes;
> +		dst.val = src.val;
> +		register_address_increment(_regs[VCPU_REGS_RSP], -op_bytes);
> +		dst.ptr = (void *) register_address(
> +			ctxt->ss_base, _regs[VCPU_REGS_RSP]);
> +		d |= Mov; /* force writeback */
> +		break;
>  	}
>   

I don't thing 'd |= Mov' is necessary any more to force writeback. 
Please check.


Also, please keep opcodes in sorted order.

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

  parent reply	other threads:[~2007-08-17 12:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-16 23:46 [Patch] (big) real mode emulation - push reg Nitin A Kamble
     [not found] ` <1187307993.10269.8.camel-mpPvwfgnXtFHIUuj5cj4Omt3HXsI98Cx0E9HWUfgJXw@public.gmane.org>
2007-08-17 12:21   ` Avi Kivity [this message]
     [not found]     ` <46C592B6.8030700-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-08-17 22:32       ` Nitin A Kamble
     [not found]         ` <1187389929.9011.18.camel-mpPvwfgnXtFHIUuj5cj4Omt3HXsI98Cx0E9HWUfgJXw@public.gmane.org>
2007-08-19  8:07           ` Avi Kivity

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=46C592B6.8030700@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=nitin.a.kamble-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=wilfred.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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