On Tue, 07/05 10:35, Daniel P. Berrange wrote:
>
> Can you backup and explain more detail what the actual problem you're trying
> to solve is. IIUC, it is related to module loading, but I'm not seeing exactly
> what it is.
This patch originated when I was researching all drivers' block_init
On Tue, Jul 05, 2016 at 10:26:56AM +0100, Daniel P. Berrange wrote:
> On Tue, Jul 05, 2016 at 11:18:29AM +0200, Alberto Garcia wrote:
> > On Tue 05 Jul 2016 10:45:21 AM CEST, Daniel P. Berrange wrote:
> >
> > > The point of using qcrypto_hash_supports() is that it isolates the
> > > block code
On Tue, Jul 05, 2016 at 04:57:58PM +0800, Fam Zheng wrote:
> On Tue, 07/05 09:45, Daniel P. Berrange wrote:
> > On Tue, Jun 28, 2016 at 09:47:47AM +0800, Fam Zheng wrote:
> > > This was the only exceptional module init function that does something
> > > else than a simple list of bdrv_register()
On Tue, Jul 05, 2016 at 11:18:29AM +0200, Alberto Garcia wrote:
> On Tue 05 Jul 2016 10:45:21 AM CEST, Daniel P. Berrange wrote:
>
> > The point of using qcrypto_hash_supports() is that it isolates the
> > block code Makefile rules from the details of the current specific
> > impl of the hash
On Tue 05 Jul 2016 10:45:21 AM CEST, Daniel P. Berrange wrote:
> The point of using qcrypto_hash_supports() is that it isolates the
> block code Makefile rules from the details of the current specific
> impl of the hash APIs in QEMU. As a prime example of why this is
> important, try rebasing to
Dear Alberto,
Alberto Garcia writes:
> On Tue 05 Jul 2016 09:58:25 AM CEST, Sascha Silbe wrote:
>
>> The quorum driver needs SHA256 which was introduced in gnutls 2.11.1.
>
> Are you sure about that?
>
> * Version 1.7.4 (released 2007-02-05)
>
> [...]
>
> ** API and ABI
On Tue, 07/05 09:45, Daniel P. Berrange wrote:
> On Tue, Jun 28, 2016 at 09:47:47AM +0800, Fam Zheng wrote:
> > This was the only exceptional module init function that does something
> > else than a simple list of bdrv_register() calls, in all the block
> > drivers.
> >
> > The
On Tue, Jun 28, 2016 at 09:47:47AM +0800, Fam Zheng wrote:
> This was the only exceptional module init function that does something
> else than a simple list of bdrv_register() calls, in all the block
> drivers.
>
> The qcrypto_hash_supports is actually a static check, determined at
> compile
On Tue 05 Jul 2016 09:58:25 AM CEST, Sascha Silbe wrote:
> The quorum driver needs SHA256 which was introduced in gnutls 2.11.1.
Are you sure about that?
* Version 1.7.4 (released 2007-02-05)
[...]
** API and ABI modifications:
GNUTLS_MAC_SHA256,
GNUTLS_MAC_SHA384,
GNUTLS_MAC_SHA512: New
On Tue, 07/05 09:58, Sascha Silbe wrote:
> Dear Fam (or Zheng?),
Hi Sascha,
Zheng is the last name here. :)
>
> Fam Zheng writes:
>
> > This was the only exceptional module init function that does something
> > else than a simple list of bdrv_register() calls, in all the
Dear Fam (or Zheng?),
Fam Zheng writes:
> This was the only exceptional module init function that does something
> else than a simple list of bdrv_register() calls, in all the block
> drivers.
>
> The qcrypto_hash_supports is actually a static check, determined at
> compile
On Sat, 07/02 14:36, Max Reitz wrote:
> On 28.06.2016 03:47, Fam Zheng wrote:
> > This was the only exceptional module init function that does something
> > else than a simple list of bdrv_register() calls, in all the block
> > drivers.
>
> This sounds like this patch specifically wants to drop
On Sat 02 Jul 2016 02:36:38 PM CEST, Max Reitz wrote:
>> This was the only exceptional module init function that does
>> something else than a simple list of bdrv_register() calls, in all
>> the block drivers.
>
> This sounds like this patch specifically wants to drop the check from
>
On 28.06.2016 03:47, Fam Zheng wrote:
> This was the only exceptional module init function that does something
> else than a simple list of bdrv_register() calls, in all the block
> drivers.
This sounds like this patch specifically wants to drop the check from
bdrv_quorum_init().
I think keeping
On Tue 28 Jun 2016 03:47:47 AM CEST, Fam Zheng wrote:
> The qcrypto_hash_supports is actually a static check, determined at
> compile time. Follow the block-job-$(CONFIG_FOO) convention for
> consistency.
>
> Signed-off-by: Fam Zheng
Oh, so we didn't see this
This was the only exceptional module init function that does something
else than a simple list of bdrv_register() calls, in all the block
drivers.
The qcrypto_hash_supports is actually a static check, determined at
compile time. Follow the block-job-$(CONFIG_FOO) convention for
consistency.
16 matches
Mail list logo