On Mon, 26 Jun 2017 23:33:48 -0300
Eduardo Habkost wrote:
> On Mon, Jun 26, 2017 at 02:28:13PM +0100, Alex Bennée wrote:
> >
> > Peter Maydell writes:
> >
> > > This patchset adds a new function cpu_generic_new()
> > > which is similar to
On Mon, Jun 26, 2017 at 02:28:13PM +0100, Alex Bennée wrote:
>
> Peter Maydell writes:
>
> > This patchset adds a new function cpu_generic_new()
> > which is similar to cpu_generic_init() except that it
> > does not realize the created CPU object. This means that
> >
Peter Maydell writes:
> This patchset adds a new function cpu_generic_new()
> which is similar to cpu_generic_init() except that it
> does not realize the created CPU object. This means that
> board code can do a "new cpu; set QOM properties; realize"
> sequence
On 21 February 2017 at 15:58, Eduardo Habkost wrote:
> On Thu, Feb 16, 2017 at 04:40:43PM +, Peter Maydell wrote:
>> I know it's only been a few days, but I just wanted to
>> say that I'd appreciate it if we could manage relatively
>> quick review on this one, since I
On Thu, Feb 16, 2017 at 04:40:43PM +, Peter Maydell wrote:
> On 13 February 2017 at 14:28, Peter Maydell wrote:
> > This patchset adds a new function cpu_generic_new()
> > which is similar to cpu_generic_init() except that it
> > does not realize the created CPU
On 13 February 2017 at 14:28, Peter Maydell wrote:
> This patchset adds a new function cpu_generic_new()
> which is similar to cpu_generic_init() except that it
> does not realize the created CPU object. This means that
> board code can do a "new cpu; set QOM properties;