public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: Mohammed Gamal <m.gamal005@gmail.com>, KVM list <kvm@vger.kernel.org>
Subject: Re: [RFC PATCH v3 0/3] Add segment limit checks to emulator
Date: Mon, 12 Jul 2010 17:49:37 +0300	[thread overview]
Message-ID: <4C3B2B81.6070109@redhat.com> (raw)
In-Reply-To: <20100712144103.GA17853@redhat.com>

On 07/12/2010 05:41 PM, Gleb Natapov wrote:
>
>> A good way to do this is to add a segment variable to 'struct
>> operand', and doing all the base adjustment at the end (instead of
>> up front as we do now).  That means we'll have the minimum number of
>> places to add checks to.
>>      
> ->read_emulated(), ->write_emulated() get liner address as a parameter
> and know nothing about 'struct operand'. Luckily emulator.c has only one
> call for each one of them, so segment checking can be done there just
> before call to the functions.
>
>    

I'd prefer a new helper (with an additional parameter) so that if a new 
call is added, we don't need to change anything.


-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2010-07-12 14:49 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-11 22:56 [RFC PATCH v3 0/3] Add segment limit checks to emulator Mohammed Gamal
2010-07-11 22:56 ` [RFC PATCH v3 1/3] Add helper methods to get segment limits Mohammed Gamal
2010-07-11 22:56 ` [RFC PATCH v3 2/3] x86 emulator: Add segment limit checking helpers Mohammed Gamal
2010-07-11 22:56 ` [RFC PATCH v3 3/3] x86 emulator: Add segment limit checks to emulator functions Mohammed Gamal
2010-07-12  6:26 ` [RFC PATCH v3 0/3] Add segment limit checks to emulator Avi Kivity
2010-07-12 12:36   ` Mohammed Gamal
2010-07-12 13:13     ` Avi Kivity
     [not found]       ` <AANLkTimHvpE05chocuoQnY0ydOMchMcIInu9QX5F_pV4@mail.gmail.com>
2010-07-12 13:51         ` Avi Kivity
2010-07-12 14:41           ` Gleb Natapov
2010-07-12 14:49             ` Avi Kivity [this message]
2010-07-24 15:45       ` Kevin O'Connor
2010-07-24 16:16         ` Kevin O'Connor
2010-07-25  8:55           ` Avi Kivity
2010-07-25 16:42             ` Kevin O'Connor
2010-07-25 17:19               ` Kevin O'Connor
2010-07-25 18:34                 ` Avi Kivity
2010-07-25 18:55                   ` Kevin O'Connor
2010-07-25  8:54         ` Avi Kivity
2010-07-25 16:23           ` Kevin O'Connor
2010-07-26 11:47             ` Avi Kivity
2010-07-26 17:47               ` Stefan Hajnoczi

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=4C3B2B81.6070109@redhat.com \
    --to=avi@redhat.com \
    --cc=gleb@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=m.gamal005@gmail.com \
    /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